commit | 0188935d55206e8c2becb29e995f166cb7040355 | [log] [tgz] |
---|---|---|
author | Tianjie Xu <xunchang@google.com> | Tue Mar 22 18:08:12 2016 -0700 |
committer | Tianjie Xu <xunchang@google.com> | Wed Mar 23 15:19:18 2016 -0700 |
tree | ab26b6bf89d0adf0b152f5dad6bf4d27107e7f5f | |
parent | f73abf36bcfd433a3fdd1664a77e8e531346c1b1 [diff] |
Skip stashing source blocks in verify mode Currently block_image_verify() stashes source blocks to /cache and in some case triggers I/O errors. To avoid this risk, We create a map from the hash value to the source blocks' range_set. When executing stash command in verify mode, source range is saved but block contents aren't stashed. And load_stash could get its value from either the stashed file from the previous update, or the contents on the source partition specified by the saved range. Bug: 27584487 Bug: 25633753 Change-Id: I775baf4bee55762b6e7b204f8294afc597afd996
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