commit | 9d33dac7f15991547de0d4b397b8de0f20f37a22 | [log] [tgz] |
---|---|---|
author | Alex Deymo <deymo@google.com> | Thu Jan 12 22:48:17 2017 +0000 |
committer | android-build-merger <android-build-merger@google.com> | Thu Jan 12 22:48:17 2017 +0000 |
tree | 14687532d378879d50e238873eff12a189c80a49 | |
parent | 866e72bf99cb9da24021f3f3a0dbea4f902c95cf [diff] | |
parent | a6adbefa2c665880da65973ddead1fab857c1c4f [diff] |
Merge changes from topic 'host_suffix_cleanup' am: 8031c2d2bb am: f8f1a25850 am: a1e336d548 am: a6adbefa2c Change-Id: Ife8bfd65d7d439fab60cd462fa272912a6fd99bf
mm -j && m ramdisk-nodeps && m recoveryimage-nodeps # To boot into the new recovery image # without flashing the recovery partition: adb reboot bootloader fastboot boot $ANDROID_PRODUCT_OUT/recovery.img
# After setting up environment and lunch. mmma -j bootable/recovery # Running the tests on device. adb root adb sync data # 32-bit device adb shell /data/nativetest/recovery_unit_test/recovery_unit_test adb shell /data/nativetest/recovery_component_test/recovery_component_test # Or 64-bit device adb shell /data/nativetest64/recovery_unit_test/recovery_unit_test adb shell /data/nativetest64/recovery_component_test/recovery_component_test
recovery-refresh
and recovery-persist
executables exist only on systems without /cache partition. And we need to follow special steps to run tests for them.
Execute the test on an A/B device first. The test should fail but it will log some contents to pmsg.
Reboot the device immediately and run the test again. The test should save the contents of pmsg buffer into /data/misc/recovery/inject.txt. Test will pass if this file has expected contents.