| BUILD.gn |
|
671 |
| lacros_resource_sizes.gni |
|
764 |
| lacros_resource_sizes.py |
Reports binary size metrics for LaCrOS build artifacts.
More information at //docs/speed/binary_size/metrics.md.
|
12267 |
| lacros_resource_sizes.pydeps |
|
691 |
| metadata.json.in |
|
97 |
| mojo_connection_lacros_launcher.py |
Helps launch lacros-chrome with mojo connection established on Linux
or Chrome OS. Use on Chrome OS is for dev purposes.
The main use case is to be able to launch lacros-chrome in a debugger.
Please first launch an ash-chrome in the background as usual except without
the '--lacros-chrome-path' argument and with an additional
'--lacros-mojo-socket-for-testing' argument pointing to a socket path:
XDG_RUNTIME_DIR=/tmp/ash_chrome_xdg_runtime ./out/ash/chrome \\
--user-data-dir=/tmp/ash-chrome --enable-wayland-server \\
--no-startup-window --enable-features=LacrosSupport \\
--lacros-mojo-socket-for-testing=/tmp/lacros.sock
Then, run this script with '-s' pointing to the same socket path used to
launch ash-chrome, followed by a command one would use to launch lacros-chrome
inside a debugger:
EGL_PLATFORM=surfaceless XDG_RUNTIME_DIR=/tmp/ash_chrome_xdg_runtime \\
./build/lacros/mojo_connection_lacros_launcher.py -s /tmp/lacros.sock
gdb --args ./out/lacros-release/chrome --user-data-dir=/tmp/lacros-chrome
|
5954 |
| OWNERS |
|
67 |
| PRESUBMIT.py |
Presubmit script for changes affecting //build/lacros |
728 |
| test_runner.py |
This script facilitates running tests for lacros on Linux.
In order to run lacros tests on Linux, please first follow bit.ly/3juQVNJ
to setup build directory with the lacros-chrome-on-linux build configuration,
and corresponding test targets are built successfully.
* Example usages:
./build/lacros/test_runner.py test out/lacros/url_unittests
./build/lacros/test_runner.py test out/lacros/browser_tests
The commands above run url_unittests and browser_tests respecitively, and more
specifically, url_unitests is executed directly while browser_tests is
executed with the latest version of prebuilt ash-chrome, and the behavior is
controlled by |_TARGETS_REQUIRE_ASH_CHROME|, and it's worth noting that the
list is maintained manually, so if you see something is wrong, please upload a
CL to fix it.
./build/lacros/test_runner.py test out/lacros/browser_tests \\
--gtest_filter=BrowserTest.Title
The above command only runs 'BrowserTest.Title', and any argument accepted by
the underlying test binary can be specified in the command.
./build/lacros/test_runner.py test out/lacros/browser_tests \\
--ash-chrome-version=793554
The above command runs tests with a given version of ash-chrome, which is
useful to reproduce test failures, the version corresponds to the commit
position of commits on the master branch, and a list of prebuilt versions can
be found at: gs://ash-chromium-on-linux-prebuilts/x86_64.
./testing/xvfb.py ./build/lacros/test_runner.py test out/lacros/browser_tests
The above command starts ash-chrome with xvfb instead of an X11 window, and
it's useful when running tests without a display attached, such as sshing.
For version skew testing when passing --ash-chrome-path-override, the runner
will try to find the ash major version and Lacros major version. If ash is
newer(major version larger), the runner will not run any tests and just
returns success.
|
21346 |
| test_runner_test.py |
|
10410 |