commit | 6b1aae376a06837d03e96fd19e842d995d967c1f | [log] [tgz] |
---|---|---|
author | Tao Bao <tbao@google.com> | Tue Sep 26 15:37:59 2017 -0700 |
committer | Tao Bao <tbao@google.com> | Thu Nov 02 16:23:58 2017 -0700 |
tree | c4eb62412169843499b196496e8d0ae0a349eb39 | |
parent | 43f194c8bc383fdda40505813db98c9f7860417b [diff] |
Add a repohook to clang-format changes. It would clang-format according to the local style file in .clang-format, unless explicitly skipped with --no-verify. An example output is as follows: [COMMIT dda6b1ee4247] test [FAILED] clang_format The following files have formatting errors: screen_ui.cpp You can run `/mnt/aosp/aosp-master/tools/repohooks/tools/clang-format.py --fix --clang-format /mnt/aosp/aosp-master/prebuilts/clang/host/linux-x86/clang-stable/bin/clang-format --git-clang-format /mnt/aosp/aosp-master/prebuilts/clang/host/linux-x86/clang-stable/bin/git-clang-format --style file --commit dda6b1ee424710760bbab4421e95239fa6a2b40d` to fix this [COMMIT be69a2c4ba16] Add a repohook to clang-format the change. [RUNNING 2/2] clang_format An automatic fix can be attempted for the "clang_format" hook. Do you want to run it? (Yes/no)? Fix successfully applied. Amend the current commit before attempting to upload again. More details about repohooks can be found at: https://android.googlesource.com/platform/tools/repohooks/ Test: `repo upload` a CL. Change-Id: Ie8203a317eb3be7acd5592e03374873997647aa0
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.
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.