commit | fbde508ace399c977f5af9b495743e0960ac6a5c | [log] [tgz] |
---|---|---|
author | Tao Bao <tbao@google.com> | Fri Nov 18 15:58:16 2016 -0800 |
committer | Tao Bao <tbao@google.com> | Fri Nov 18 16:00:23 2016 -0800 |
tree | b4e36afaeb5140ebc8dd7ff18ac7d685f8beae34 | |
parent | 6fd51ffdaa3563322ce30a7fd225889c9c3c2204 [diff] |
bootloader_message: Remove the no-op blank line. This single blank line was introduced by some cherry-pick, which is causing merge conflicts. Test: N/A Change-Id: Ida527b76fca7cc916499c5f888476c8e51ba3eaa
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.