commit | b619fe60fd0d5ce4f3d7aac50ebdd4557a30e600 | [log] [tgz] |
---|---|---|
author | Tao Bao <tbao@google.com> | Mon Nov 21 19:27:37 2016 +0000 |
committer | android-build-merger <android-build-merger@google.com> | Mon Nov 21 19:27:37 2016 +0000 |
tree | d37aa9fbeb45b902598b2628bab1bc28b68a60ca | |
parent | ef77aa2b73af622a154bd937bd31e5bc0b84681a [diff] | |
parent | 21a10e2cfafbb84e90c14f643ad0e55cb97e4415 [diff] |
Merge "Fail gracefully when we fail to fork the update binary" am: 340a2d364f am: 2a962adc85 am: 5713071c81 am: 21a10e2cfa Change-Id: I00b662c9c7bcb0385444d4e548dc8e7f56f01735
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.