commit | 17e316cce0047dcb892fb6dae9924cf6e0b41516 | [log] [tgz] |
---|---|---|
author | Tianjie Xu <xunchang@google.com> | Wed Sep 28 11:42:17 2016 -0700 |
committer | Tianjie Xu <xunchang@google.com> | Fri Sep 30 11:18:01 2016 -0700 |
tree | ed0fa36534423e5fa55c22afa38248bd1dd303c1 | |
parent | 4c3f6ab8f7be21acf33ff0dfabec9047aac36e3c [diff] |
Turn on -Werror for recovery Also remove the 0xff comparison when validating the bootloader message fields. As the fields won't be erased to 0xff after we remove the MTD support. Bug: 28202046 Test: The recovery folder compiles for aosp_x86-eng Change-Id: Ibb30ea1b2b28676fb08c7e92a1e5f7b6ef3247ab (cherry picked from commit 7aa88748f6ec4e53333d1a15747bc44826ccc410)
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