In the process of running and testing VTS, it was found that the final result only ran 6 modules, and the log contained the following contents:
armeabi-v7a VtsHalGnssV1_0Target: VtsHalGnssV1_0Target:
Error executing adb cmd 'adb -s WT123456789 shell "stop"'. ret: 1, stdout: , stderr: stop: must be root
armeabi-v7a VtsHalGatekeeperV1_0Target: VtsHalGatekeeperV1_0Target:
Error executing adb cmd 'adb -s WT123456789 shell "stop"'. ret: 1, stdout: , stderr: stop: must be root
armeabi-v7a VtsHalGraphicsComposerV2_3Target: VtsHalGraphicsComposerV2_3Target:
Error executing adb cmd 'adb -s 0123456789ABCDEF shell "stop"'. ret: 1, stdout: , stderr: stop: must be root
Copy the code[ro.system.build.type]: [user]
For other projects that can normally run VTS tests, this property should be [userdebug]
Therefore, the basic judgment is that boot-debug.img is abnormal. Later, the following problems are found because boot-debug.img provides the wrong exception:
$fastboot flash boot boot-debug.img
Invalid sparse file format at header magic
Sending sparse 'boot'1/1 (8932 KB) OKAY [0.305s] Writing'boot' FAILED (remote: 'sparse image size span overflow.')
fastboot: error: Command failed
Copy the code