diff options
| author | Roland Levillain <rpl@google.com> | 2019-10-03 16:03:09 +0100 |
|---|---|---|
| committer | Roland Levillain <rpl@google.com> | 2019-10-04 10:23:31 +0000 |
| commit | 31e284b995807271065f7cdc94f02fe3dc2c2e2f (patch) | |
| tree | 5c2e19759131038301a9bd1dbe36e66e4b634b80 /test/ProfileTestMultiDex | |
| parent | 712fa800b2b78e527d36c88dc369bf4b723587ea (diff) | |
Make ART chroot setup & sync scripts a bit more robust.
Before this change, if one forgot to run
`art/tools/setup-buildbot-device.sh` before running
`art/tools/buildbot-sync.sh`, the tree on the device under
`$ART_TEST_CHROOT` would become messy (as the contents of
`$ANDROID_PRODUCT_OUT/system` and `$ANDROID_PRODUCT_OUT/data` would be
directly copied into `$ART_TEST_CHROOT`) and scripts
`tools/teardown-buildbot-device.sh` and
`art/tools/cleanup-buildbot-device.sh` would not work correctly.
To avoid that issue, have `tools/buildbot-sync.sh` create all the
expected directories under `$ART_TEST_CHROOT` prior to pushing files
into them, so that the behavior of `tools/buildbot-sync.sh` is
independent of whether `art/tools/setup-buildbot-device.sh` had run
before or not.
Test: Check that running:
`art/tools/buildbot-sync.sh && art/tools/setup-buildbot-device.sh`
produces the same effect as running:
`art/tools/setup-buildbot-device.sh && art/tools/buildbot-sync.sh`
Bug: 34729697
Bug: 121117762
Change-Id: Ieebb3588648f2f61efaa82fb25078e0018db97be
Diffstat (limited to 'test/ProfileTestMultiDex')
0 files changed, 0 insertions, 0 deletions