No description
8ed9738b62
When using AVB, PRODUCT_SUPPORTS_VERITY is not set so check for BOARD_ENABLE_AVB as well. Also AVB sets up the root filesystem as 'vroot' so map that to 'system' since this is what is expected. Managed to test at least that the code is at least compiled in: $ fastboot --set-active=_a Setting current slot to 'a'... OKAY [ 0.023s] finished. total time: 0.023s $ fastboot reboot rebooting... finished. total time: 0.050s $ adb wait-for-device $ adb logcat |grep update_verifier 03-04 05:28:56.773 630 630 I /system/bin/update_verifier: Started with arg 1: nonencrypted 03-04 05:28:56.776 630 630 I /system/bin/update_verifier: Booting slot 0: isSlotMarkedSuccessful=0 03-04 05:28:56.776 630 630 W /system/bin/update_verifier: Failed to open /data/ota_package/care_map.txt: No such file or directory 03-04 05:28:56.788 630 630 I /system/bin/update_verifier: Marked slot 0 as booted successfully. 03-04 05:28:56.788 630 630 I /system/bin/update_verifier: Leaving update_verifier. Bug: None Test: Manually tested on device using AVB bootloader. Change-Id: I13c0fe1cc5d0f397e36f5e62fcc05c8dfee5fd85 |
||
|---|---|---|
| applypatch | ||
| boot_control | ||
| bootloader_message | ||
| edify | ||
| etc | ||
| fonts | ||
| minadbd | ||
| minui | ||
| otafault | ||
| otautil | ||
| private | ||
| res-hdpi/images | ||
| res-mdpi/images | ||
| res-xhdpi/images | ||
| res-xxhdpi/images | ||
| res-xxxhdpi/images | ||
| tests | ||
| tools | ||
| uncrypt | ||
| update_verifier | ||
| updater | ||
| .clang-format | ||
| adb_install.cpp | ||
| adb_install.h | ||
| Android.bp | ||
| Android.mk | ||
| asn1_decoder.cpp | ||
| asn1_decoder.h | ||
| bootloader.h | ||
| CleanSpec.mk | ||
| common.h | ||
| default_device.cpp | ||
| device.cpp | ||
| device.h | ||
| error_code.h | ||
| fuse_sdcard_provider.cpp | ||
| fuse_sdcard_provider.h | ||
| fuse_sideload.cpp | ||
| fuse_sideload.h | ||
| install.cpp | ||
| install.h | ||
| interlace-frames.py | ||
| mounts.cpp | ||
| mounts.h | ||
| NOTICE | ||
| print_sha1.h | ||
| README.md | ||
| recovery-persist.cpp | ||
| recovery-persist.rc | ||
| recovery-refresh.cpp | ||
| recovery-refresh.rc | ||
| recovery.cpp | ||
| res-560dpi | ||
| roots.cpp | ||
| roots.h | ||
| rotate_logs.cpp | ||
| rotate_logs.h | ||
| screen_ui.cpp | ||
| screen_ui.h | ||
| stub_ui.h | ||
| ui.cpp | ||
| ui.h | ||
| verifier.cpp | ||
| verifier.h | ||
| wear_touch.cpp | ||
| wear_touch.h | ||
| wear_ui.cpp | ||
| wear_ui.h | ||
The Recovery Image
Quick turn-around testing
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
Running the tests
# 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
Running the manual tests
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.
ResourceTest validates whether the png files are qualified as background text
image under recovery.
1. `adb sync data` to make sure the test-dir has the images to test.
2. The test will automatically pickup and verify all `_text.png` files in
the test dir.