commit | d0de070a390d4825cbbb6eeed5433720045f26eb | [log] [tgz] |
---|---|---|
author | Tao Bao <tbao@google.com> | Tue Nov 29 11:54:04 2016 -0800 |
committer | Tao Bao <tbao@google.com> | Thu Dec 01 00:00:25 2016 -0800 |
tree | 17f62871a8145488c6516f106df49791a5e7420a | |
parent | d514b61b31ca2b4e2d69d72d4399d37f8ada25c4 [diff] |
updater: Fix inconsistent code. Commit 81e54eddd4132895d70ab8b2307c693311799e05 introduced the inconsistency when resolving the merge conflict into master. Test: mmma bootable/recovery Change-Id: I43b7ec76a7eee000708cdca60bd372173e1fac2f
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.