分类： VTS

Q版本刷GSI注意事项

问题描述

 Q版本要跑cts-on-gsi和跑VTS的机器刷GSI方式有差异，请参考下表。
 前提条件：
 adb和fastboot需要升级到最新版本，否则执行fastboot reboot fastboot会出现unknown command的错误。
 Google官网最新platform tools下载路径如下：

[VTS 10.0-R2]VtsTrebleFrameworkVintfTest VtsTrebleFrameworkVintfTest#SystemVendorTest.ServedHwbinderHalsAreInManifest_32bit fail

问题描述

VtsTrebleFrameworkVintfTest VtsTrebleFrameworkVintfTest#SystemVendorTest.ServedHwbinderHalsAreInManifest_32bit fail
VtsTrebleFrameworkVintfTest#SystemVendorTest.ServedHwbinderHalsAreInManifest_64bit fail
test/vts-testcase/hal/treble/vintf/SystemVendorTest.cpp:131
Expected: (manifest_hwbinder_hals.find(name)) != (manifest_hwbinder_hals.end()), actual: 8-byte object <98-F6 9A-D4 7F-00 00-00> vs 8-byte object <98-F6 9A-D4 7F-00 00-00>

VtsHalRadioV1_0Target模块all case failed

问题描述

VtsHalRadioV1_0Target模块all case failed

Fail1:

hardware/interfaces/radio/1.0/vts/functional/radio_hidl_hal_test.cpp:75 Expected equality of these values: std::cv_status::no_timeout Which is: 4-byte object <00-00 00-00> wait() Which is: 4-byte object <01-00 00-00> hardware/interfaces/radio/1.0/vts/functional/radio_hidl_hal_test.cpp:42 Expected equality of these values: serial Which is: 66098897 radioRsp->rspInfo.serial Which is: 0 hardware/interfaces/radio/1.0/vts/functional/radio_hidl_hal_test.cpp:46 Expected equality of these values: CardState::PRESENT Which is: 4-byte object <01-00 00-00> cardStatus.cardState Which is: 4-byte object <00-00 00-00>

继续阅读“VtsHalRadioV1_0Target模块all case failed”

VtsKernelNetTest#testKernelNetworking#testProcNetIcmp6 (ping6_test.Ping6Test) fail

问题描述

如果project使用kernel-3.18，在跑vtskernelnettest测项中，如果出现类似backtrace
        FAIL: testProcNetIcmp6 (ping6_test.Ping6Test)
----------------------------------------------------------------------
Traceback (most recent call last):
File "/data/nativetest64/kernel_net_tests/kernel_net_tests/runfiles/ping6_test.py", line 807, in testProcNetIcmp6
txmem=0, rxmem=0)
File "/data/nativetest64/kernel_net_tests/kernel_net_tests/runfiles/ping6_test.py", line 333, in CheckSockStatFile
self.fail("Cound not find socket matching %s" % expected)
AssertionError: Cound not find socket matching ['000080FE00000000FF000000016400FE:D00D', '000002FF000000000000000001000000:DEAD', '01', '00000000:00000000', '0', '2', '0']
 需要申请patch。

继续阅读“VtsKernelNetTest#testKernelNetworking#testProcNetIcmp6 (ping6_test.Ping6Test) fail”

VTS Waiver reduction and May release

VTS Waiver reduction and May release VTS豁免缩减和5月份Release

 

VtsHalRadioV1_2Target包测试多条fail

问题描述

 VTS test request plug in SIMs in all SIM slots from Android P, but they doesn't cover the VSIM case, there is no way to plug in SIM in the vsim only slot. So we enable modem VSIM at the VSIM only slot if there is no MTK framework.
VTS测试从Android P开始要求插卡测试，而Google没有考虑VSIM的情况，因为VSIM only的slot不能插实体卡，造成VTS测试fail。所以判断如果没有上层MTK framework的话，认为是GSI，在VSIM only的操作打开modem VSIM。

继续阅读“VtsHalRadioV1_2Target包测试多条fail”

Android O/P版本更新patch后刷GSI后无法开机问题

问题描述

     近期大量更新patch后，客户VTS 和 CTS-on-GSI测试，刷GSI无法开机问题，都是由于hidl的改动造成的。这个需要google出新的GSI来解决。
[Related Patch]
o1.mp1 ALPS04304953
o1.mp2 ALPS04308385
     上述两笔patch都有涉及hidl的修改，请客户确认是否上述两笔Patch导致的。

继续阅读“Android O/P版本更新patch后刷GSI后无法开机问题”

【VTS_P version】VtsTrebleVendorVintfTest 跟hash相关fail

问题描述

 VtsTrebleVendorVintfTest测试时可能会遭遇以下两种情况报hash的错误：
Case1：
01-05 12:25:53 D/ModuleListener: ModuleListener.testStarted(VtsTrebleVendorVintfTest#DeviceManifest/SingleManifestTest.InterfacesAreReleased/0_32bit)
01-05 12:25:53 D/ModuleListener: ModuleListener.testFailed(VtsTrebleVendorVintfTest#DeviceManifest/SingleManifestTest.InterfacesAreReleased/0_32bit, test/vts-testcase/hal/treble/vintf/SingleManifestTest.cpp:57
Failed
vendor.sw.swfingerprint@1.0::ISwfingerprint has an empty hash. This is because it was compiled without being frozen in a corresponding current.txt file.
test/vts-testcase/hal/treble/vintf/SingleManifestTest.cpp:57
Failed
Case2：

vendor.oppo.hardware.biometrics.fingerprint@2.1::IBiometricsFingerprint has an empty hash. This is because it was compiled without being frozen in a corresponding current.txt file.

继续阅读“【VTS_P version】VtsTrebleVendorVintfTest 跟hash相关fail”

【VTS 9.0 R4】VtsTrebleVendorVintfTest#DeviceManifest/SingleManifestTest两个fail项

问题描述

VtsTrebleVendorVintfTest#DeviceManifest/SingleManifestTest.HalsAreServed/0_64bit
VtsTrebleVendorVintfTest#DeviceManifest/SingleManifestTest.InterfacesAreReleased/0_64bit
VtsTrebleVendorVintfTest#DeviceManifest/SingleManifestTest.HalsAreServed/0_32bit
VtsTrebleVendorVintfTest#DeviceManifest/SingleManifestTest.InterfacesAreReleased/0_32bit
fail
test/vts-testcase/hal/treble/vintf/SingleManifestTest.cpp:45

 

解决方案

继续阅读“【VTS 9.0 R4】VtsTrebleVendorVintfTest#DeviceManifest/SingleManifestTest两个fail项”

Android 9.0 8.1 and 8.0 VTS 测试工具12月份下载更新

  • The December releases of the Vendor Test Suite (VTS) for Android 9.0, 8.1, and 8.0 have been released on the GMS help center; see the android-partners announcement for more details. These releases contain continuous improvements of tests and test infrastructure and include security patch support up to the January 2019 Public Security Bulletin.

继续阅读“Android 9.0 8.1 and 8.0 VTS 测试工具12月份下载更新”

【VTS 8.1_r6】CtsShortcutManagerTestCases android.content.pm.cts.shortcutmanager.ShortcutManagerFakingPublisherTest#testSpoofingPublisher fail

问题描述

 VTS 8.1_r6,CtsShortcutManagerTestCases android.content.pm.cts.shortcutmanager.ShortcutManagerFakingPublisherTest#testSpoofingPublisher fail

继续阅读“【VTS 8.1_r6】CtsShortcutManagerTestCases android.content.pm.cts.shortcutmanager.ShortcutManagerFakingPublisherTest#testSpoofingPublisher fail”