commit | 7aa88748f6ec4e53333d1a15747bc44826ccc410 | [log] [tgz] |
---|---|---|
author | Tianjie Xu <xunchang@google.com> | Wed Sep 28 11:42:17 2016 -0700 |
committer | Tianjie Xu <xunchang@google.com> | Thu Sep 29 19:21:24 2016 -0700 |
tree | 98edb6021753eec604eb1105c45b4e8e7fa569a3 | |
parent | af8b9363c6a5efaa060ed18d30ac424306541e28 [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
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