- Instead of parsing *.isolated files, use isolate remap
to create a temporary dependency dir.
- Add an exclusion list to filter dependecies at a finer grain
than what's specified in isolate files.
- Convert base_unittests and unit_tests to use isolate.
This adds an additional 50MB to the dependency size due
to many small directories not specified in the exclusion list.
BUG=249870
Review URL: https://chromiumcodereview.appspot.com/18233018
git-svn-id: http://src.chromium.org/svn/trunk/src/build@211350 4ff67af0-8c30-449e-8e8b-ad334ec8d88c
asan_symbolize.py is used for the logcat stacks using the special ASan format.
tombstones.py is used to manage tombstones files in devices.
symbolize.py is used for stack traces generated by base/debug/stack_trace_android.cc
BUG=234973
Review URL: https://chromiumcodereview.appspot.com/18473004
git-svn-id: http://src.chromium.org/svn/trunk/src/build@211134 4ff67af0-8c30-449e-8e8b-ad334ec8d88c
The script now returns exit codes based on what occurred in the
test. Exit codes:
0 -- normal
1 -- fail/crash
88 -- warning
In addition, the scripts now handle DeviceUnresponsiveError by
returning a warning exit code overall, rather than silently moving
on.
BUG=170477, 258171
Review URL: https://chromiumcodereview.appspot.com/18323020
git-svn-id: http://src.chromium.org/svn/trunk/src/build@210749 4ff67af0-8c30-449e-8e8b-ad334ec8d88c
Currently, we are generating v14 layout and style resources from v17
resources by replacing Start and End attributes to Left and Right
attributes. However, it is not necessary for all cases, so make an
option to disable generate_v14_compatible_resources.py script and
only verify that there is no RTL attributes in the pre-v17 resources.
BUG=247049
Review URL: https://chromiumcodereview.appspot.com/18653002
git-svn-id: http://src.chromium.org/svn/trunk/src/build@210555 4ff67af0-8c30-449e-8e8b-ad334ec8d88c
This relands r209945.
r242846 slightly changed the CLI <-> device daemon message sequence which made
the following check fail in case the device daemon was started but already
running on the device: device_forwarder_main.cc:10: CHECK_GT(bytes_read, 0).
This was actually caused by an unexposed long standing issue in daemon.cc.
ConnectToUnixDomainSocket() is performing a hand check to make sure that the
CLI is connecting to the forwarder daemon. While doing this hand check, rather
than only reading the expected fixed-size message, the function was reading all
the available bytes in the socket thus consuming the client data.
BUG=242846
R=bulach@chromium.org
Review URL: https://codereview.chromium.org/18635005
git-svn-id: http://src.chromium.org/svn/trunk/src/build@210273 4ff67af0-8c30-449e-8e8b-ad334ec8d88c
Causes android buildbots to spew deprecation warnings.
> Creates a new test running script test_runner.py
>
> This new script serves as a unified entry point for all tests. The
> existing scripts are now just wrappers around the new script. Old
> commands should thus still work, but you can now make use of the
> new script to run various types of tests.
>
> There are a few TODOs left:
> * Add options to run Monkey tests.
>
> Miscellaneous notes:
> * --python_test_root is now a required flag when Python host-driven
> tests are being run.
>
> BUG=248351
>
> Review URL: https://chromiumcodereview.appspot.com/15942016TBR=gkanwar@google.com
Review URL: https://codereview.chromium.org/18732002
git-svn-id: http://src.chromium.org/svn/trunk/src/build@210251 4ff67af0-8c30-449e-8e8b-ad334ec8d88c
This new script serves as a unified entry point for all tests. The
existing scripts are now just wrappers around the new script. Old
commands should thus still work, but you can now make use of the
new script to run various types of tests.
There are a few TODOs left:
* Add options to run Monkey tests.
Miscellaneous notes:
* --python_test_root is now a required flag when Python host-driven
tests are being run.
BUG=248351
Review URL: https://chromiumcodereview.appspot.com/15942016
git-svn-id: http://src.chromium.org/svn/trunk/src/build@210035 4ff67af0-8c30-449e-8e8b-ad334ec8d88c
When doing a gyp_managed_install, we install APKs to the attached
device. Currently this can fail in many ways (no device attached,
multiple devices attached, device offline, device doesn't have root,
etc.). In addition, we need to detect changes to the attached device
(particularly when the device is switched, when an APK is
uninstalled/updated).
The current approach is to check all this information in the action
interacting with the device. This means that when there is some
problem we print the same warning messages for every APK that is built,
and, in some cases, multiple times for each APK. Also, we have to run
every install/push action every build because we detect changes to the
attached device in that action.
This change creates a new build action, "get device configurations".
This action inspects the attached devices, filters out offline devices,
filters out devices without root, and then writes a configuration
file with the id+metadata for the first non-filtered device. This
configuration is then used by each of the build steps that interacts
with the device. This consolidates all the device checking to a single
place, and the build actions don't need to do any checking. In
addition, to detect changes in the attached device, we only need to run
this single action every build and the install/push actions will only
change when the device/metadata changes.
Also, with this change we can now gracefully handle the case where
multiple devices are attached (currently just write the configuration
for the first valid device and install to that one).
Review URL: https://chromiumcodereview.appspot.com/16831013
git-svn-id: http://src.chromium.org/svn/trunk/src/build@209582 4ff67af0-8c30-449e-8e8b-ad334ec8d88c
sivachandra@chromium.org
scherkus@chromium.org
frankf@chromium.org
navabi@google.com
simonhatch@chromium.org
pliard@chromium.org
bulach@chromium.org
craigdh@chromium.org
gkanwar@google.com
joaodasilva@chromium.org
nduca@chromium.org
kkimlabs@chromium.org
hellner@chromium.org
ilevy@chromium.org
hashimoto@chromium.org
cjhopman@chromium.org
aurimas@chromium.org
tfarina@chromium.org
wangxianzhu@chromium.org
kinuko@chromium.org