Don't try to make /system on device writable when syncing ART to chroot dir.
When using a chroot dir for ART testing, we are only pushing files to
directory $ART_TEST_CHROOT (which is expected to be under /data on the
device) -- /system is left untouched, which means we do not need to
try and make it writable before syncing ART to the device for testing
purposes.
Note that skipping this step is especially useful in the case of
chroot-based testing, as making /system writable requires a reboot on
most devices nowadays (it's needed after running
`adb disable-verity`), whichs resets some of the chroot setup (and
thus requires running the chroot setup script again).
Test: Rely on the ART Buildbot
Bug: 34729697
Change-Id: Id4e4ad93a888a1180c0502e541b9497cfa58d211
diff --git a/Android.mk b/Android.mk
index 1c94629..19c65a1 100644
--- a/Android.mk
+++ b/Android.mk
@@ -98,6 +98,7 @@
include $(art_path)/build/Android.gtest.mk
include $(art_path)/test/Android.run-test.mk
+# Make sure /system is writable on the device.
TEST_ART_ADB_ROOT_AND_REMOUNT := \
(adb root && \
adb wait-for-device remount && \
@@ -122,8 +123,10 @@
$(TEST_ART_ADB_ROOT_AND_REMOUNT)
adb sync system && adb sync data
else
+# TEST_ART_ADB_ROOT_AND_REMOUNT is not needed here, as we are only
+# pushing things to the chroot dir, which is expected to be under
+# /data on the device.
test-art-target-sync: $(TEST_ART_TARGET_SYNC_DEPS)
- $(TEST_ART_ADB_ROOT_AND_REMOUNT)
adb wait-for-device
adb push $(PRODUCT_OUT)/system $(ART_TEST_CHROOT)/
adb push $(PRODUCT_OUT)/data $(ART_TEST_CHROOT)/