commit | b99b9099e8f794170814cd5c03ffd67a8b56466a | [log] [tgz] |
---|---|---|
author | Tao Bao <tbao@google.com> | Mon Nov 14 18:49:55 2016 +0000 |
committer | android-build-merger <android-build-merger@google.com> | Mon Nov 14 18:49:55 2016 +0000 |
tree | 71866e8a15872238f16ddd7358618942793e59dc | |
parent | 0d4c31a9952a9cf10750d45f003d1472979a33f5 [diff] | |
parent | c6bed0ab3f9bb1b2858ae5731e299974843f8e49 [diff] |
Merge "Fix "ordered comparison between pointer and zero"." am: a844bc9649 am: 08c4130493 am: 0f81984970 am: c6bed0ab3f Change-Id: I95702aa4777ac1a8b85b8458c7ab4d1f3a1d365d
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.