分类： Android

[CTS11R1]CTSDeqpTestCases fail

问题描述

CTSDeqpTestCases

arm64-v8a dEQP-VK dEQP-VK.wsi.android.swapchain.create#image_format
FAILURE: === with config {glformat=,rotation=unspecified,surfacetype=window,required=false} ===
ResourceError: vk.createSwapchainKHR(device, pCreateInfo, pAllocator, &object): VK_ERROR_OUT_OF_DEVICE_MEMORY at vkRefUtilImpl.inl:329
12-09 07:20:35.645   816   895 E Gralloc4: buffer descriptor contains invalid usage bits 0xffff00000000
12-09 07:20:35.645   816   895 E GraphicBufferAllocator: Failed to allocate (1080 x 2285) layerCount 1 format 22 usage ffffffff80000b00: -22

[VTS11R2] vts_treble_sys_prop_test-__main__.VtsTrebleSysPropTest#testVendorPropertyNames fail

问题描述

 vts_treble_sys_prop_test-__main__.VtsTrebleSysPropTest#testVendorPropertyNames
FAILURE: Traceback (most recent call last):
  File "/home/ceshi/cts/vts/11r1/daily/android-vts/testcases/vts_treble_sys_prop_test/x86_64/vts_treble_sys_prop_test/vts_treble_sys_prop_test.py", line 277, in testVendorPropertyNames
  File "/home/ceshi/cts/vts/11r1/daily/android-vts/testcases/vts_treble_sys_prop_test/x86_64/vts_treble_sys_prop_test/vts_treble_sys_prop_test.py", line 237, in _TestVendorOrOdmPropertyNames
AssertionError: 1 != 0 : vendor properties (persist.bluetooth.a2dp_aac_vbr.enable) have wrong namespace

[VTS11R2]AudioHidlDevice/AudioHidlDeviceTest#CloseDeviceWithOpenedInputStreams/0_default_primary fail

问题描述

VtsHalAudioV6_0TargetTest
 AudioHidlDevice/AudioHidlDeviceTest#CloseDeviceWithOpenedInputStreams/0_default_primary
FAILURE: hardware/interfaces/audio/core/all-versions/vts/functional/AudioPrimaryHidlHalTest.h:835: Failure
Expected success: *res
Actual: INVALID_ARGUMENTS
hardware/interfaces/audio/core/all-versions/vts/functional/6.0/AudioPrimaryHidlHalTest.cpp:130: Failure
Expected: helper.open( [&](AudioIoHandle handle, AudioConfig config, auto cb) { return getDevice()->openInputStream(handle, address, config, flags, initMetadata, cb); }, config, &res, &suggestedConfig) doesn't generate new fatal failures in the current thread.
Actual: it does.

解决方案

[VTS11R1]VtsTrebleFrameworkVintfTest#SystemVendorTest.ServedHwbinderHalsAreInManifest_32bit fail

问题描述

VtsTrebleFrameworkVintfTest
VtsTrebleFrameworkVintfTest#SystemVendorTest.ServedHwbinderHalsAreInManifest_32bit fail:
test/vts-testcase/hal/treble/vintf/SystemVendorTest.cpp:131
Expected: (manifest_hwbinder_hals.find(name)) != (manifest_hwbinder_hals.end()), actual: 4-byte object <B8-B9 B1-FF> vs 4-byte object <B8-B9 B1-FF>
vendor.kyocera.hardware.display@1.0::IDisplay/default is being served, but it is not in a manifest.
test/vts-testcase/hal/treble/vintf/SystemVendorTest.cpp:131
Expected: (manifest_hwbinder_hals.find(name)) != (manifest_hwbinder_hals.end()), actual: 4-byte object <B8-B9 B1-FF> vs 4-byte object <B8-B9 B1-FF>
vendor.mediatek.hardware.mtkradioex@1.4::IMtkRadioEx/imsSlot1 is being served, but it is not in a manifest.
test/vts-testcase/hal/treble/vintf/SystemVendorTest.cpp:131
Expected: (manifest_hwbinder_hals.find(name)) != (manifest_hwbinder_hals.end()), actual: 4-byte object <B8-B9 B1-FF> vs 4-byte object <B8-B9 B1-FF>
vendor.mediatek.hardware.mtkradioex@1.4::IMtkRadioEx/mtkAssist1 is being served, but it is not in a manifest.
test/vts-testcase/hal/treble/vintf/SystemVendorTest.cpp:131
Expected: (manifest_hwbinder_hals.find(name)) != (manifest_hwbinder_hals.end()), actual: 4-byte object <B8-B9 B1-FF> vs 4-byte object <B8-B9 B1-FF>
vendor.mediatek.hardware.mtkradioex@1.4::IMtkRadioEx/mtkCap1 is being served, but it is not in a manifest.
test/vts-testcase/hal/treble/vintf/SystemVendorTest.cpp:131
Expected: (manifest_hwbinder_hals.find(name)) != (manifest_hwbinder_hals.end()), actual: 4-byte object <B8-B9 B1-FF> vs 4-byte object <B8-B9 B1-FF>
vendor.mediatek.hardware.mtkradioex@1.4::IMtkRadioEx/mtkEm1 is being served, but it is not in a manifest.
test/vts-testcase/hal/treble/vintf/SystemVendorTest.cpp:131
Expected: (manifest_hwbinder_hals.find(name)) != (manifest_hwbinder_hals.end()), actual: 4-byte object <B8-B9 B1-FF> vs 4-byte object <B8-B9 B1-FF>
vendor.mediatek.hardware.mtkradioex@1.4::IMtkRadioEx/mtkRcs1 is being served, but it is not in a manifest.
test/vts-testcase/hal/treble/vintf/SystemVendorTest.cpp:131
Expected: (manifest_hwbinder_hals.find(name)) != (manifest_hwbinder_hals.end()), actual: 4-byte object <B8-B9 B1-FF> vs 4-byte object <B8-B9 B1-FF>
vendor.mediatek.hardware.mtkradioex@1.4::IMtkRadioEx/mtkSe1 is being served, but it is not in a manifest.
test/vts-testcase/hal/treble/vintf/SystemVendorTest.cpp:131
Expected: (manifest_hwbinder_hals.find(name)) != (manifest_hwbinder_hals.end()), actual: 4-byte object <B8-B9 B1-FF> vs 4-byte object <B8-B9 B1-FF>
vendor.mediatek.hardware.mtkradioex@1.4::IMtkRadioEx/mtkSlot1 is being served, but it is not in a manifest.
test/vts-testcase/hal/treble/vintf/SystemVendorTest.cpp:131
Expected: (manifest_hwbinder_hals.find(name)) != (manifest_hwbinder_hals.end()), actual: 4-byte object <B8-B9 B1-FF> vs 4-byte object <B8-B9 B1-FF>
vendor.mediatek.hardware.mtkradioex@1.5::IMtkRadioEx/imsSlot1 is being served, but it is not in a manifest.
test/vts-testcase/hal/treble/vintf/SystemVendorTest.cpp:131
Expected: (manifest_hwbinder_hals.find(name)) != (manifest_hwbinder_hals.end()), actual: 4-byte object <B8-B9 B1-FF> vs 4-byte object <B8-B9 B1-FF>
vendor.mediatek.hardware.mtkradioex@1.5::IMtkRadioEx/mtkAssist1 is being served, but it is not in a manifest.
test/vts-testcase/hal/treble/vintf/SystemVendorTest.cpp:131
Expected: (manifest_hwbinder_hals.find(name)) != (manifest_hwbinder_hals.end()), actual: 4-byte object <B8-B9 B1-FF> vs 4-byte object <B8-B9 B1-FF>
vendor.mediatek.hardware.mtkradioex@1.5::IMtkRadioEx/mtkCap1 is being served, but it is not in a manifest.
test/vts-testcase/hal/treble/vintf/SystemVendorTest.cpp:131
Expected: (manifest_hwbinder_hals.find(name)) != (manifest_hwbinder_hals.end()), actual: 4-byte object <B8-B9 B1-FF> vs 4-byte object <B8-B9 B1-FF>
vendor.mediatek.hardware.mtkradioex@1.5::IMtkRadioEx/mtkEm1 is being served, but it is not in a manifest.
test/vts-testcase/hal/treble/vintf/SystemVendorTest.cpp:131
Expected: (manifest_hwbinder_hals.find(name)) != (manifest_hwbinder_hals.end()), actual: 4-byte object <B8-B9 B1-FF> vs 4-byte object <B8-B9 B1-FF>
vendor.mediatek.hardware.mtkradioex@1.5::IMtkRadioEx/mtkRcs1 is being served, but it is not in a manifest.
test/vts-testcase/hal/treble/vintf/SystemVendorTest.cpp:131
Expected: (manifest_hwbinder_hals.find(name)) != (manifest_hwbinder_hals.end()), actual: 4-byte object <B8-B9 B1-FF> vs 4-byte object <B8-B9 B1-FF>
vendor.mediatek.hardware.mtkradioex@1.5::IMtkRadioEx/mtkSe1 is being served, but it is not in a manifest.
test/vts-testcase/hal/treble/vintf/SystemVendorTest.cpp:131
Expected: (manifest_hwbinder_hals.find(name)) != (manifest_hwbinder_hals.end()), actual: 4-byte object <B8-B9 B1-FF> vs 4-byte object <B8-B9 B1-FF>
vendor.mediatek.hardware.mtkradioex@1.5::IMtkRadioEx/mtkSlot1 is being served, but it is not in a manifest.

解决方案

继续阅读“[VTS11R1]VtsTrebleFrameworkVintfTest#SystemVendorTest.ServedHwbinderHalsAreInManifest_32bit fail”

[CTS11R1]android.media.cts.DecoderTestAacDrc#testDecodeAacDrcLevelM4a fail

问题描述

 CtsMediaTestCases
android.media.cts.DecoderTestAacDrc#testDecodeAacDrcLevelM4a
FAILURE: java.lang.NullPointerException: Attempt to invoke virtual method 'int java.lang.Integer.intValue()' on a null object reference

解决方案

[VTS 9.0-R14]VtsTrebleFrameworkVintfTest#SystemVendorTest.ServedHwbinderHalsAreInManifest_32bit

问题描述

VtsTrebleFrameworkVintfTest
VtsTrebleFrameworkVintfTest#SystemVendorTest.ServedHwbinderHalsAreInManifest_32bit
fail: test/vts-testcase/hal/treble/vintf/SystemVendorTest.cpp:78
Expected: (manifest_hwbinder_hals_.find(name)) != (manifest_hwbinder_hals_.end()), actual: 4-byte object <78-67 8F-BE> vs 4-byte object <78-67 8F-BE>
vendor.mediatek.hardware.radio@3.3::IRadio/imsrild1 is being served, but it is not in a manifest.
test/vts-testcase/hal/treble/vintf/SystemVendorTest.cpp:78
Expected: (manifest_hwbinder_hals_.find(name)) != (manifest_hwbinder_hals_.end()), actual: 4-byte object <78-67 8F-BE> vs 4-byte object <78-67 8F-BE>
vendor.mediatek.hardware.radio@3.3::IRadio/imsrild2 is being served, but it is not in a manifest.

[GTS8.0R1-出国内]com.google.android.gts.devicepolicy.DeviceOwnerTest#testFactoryResetProtection fail

问题描述

GtsGmscoreHostTestCases
com.android.compatibility.common.tradefed.testtype.JarHostTest com.google.android.gts.devicepolicy.DeviceOwnerTest#testFactoryResetProtection
FAILURE: junit.framework.AssertionFailedError: com.google.android.gts.deviceowner.FactoryResetProtectionTest failed.

查看了源码，发现有两个文件夹：

1.vendor\google\products\gms_overlay：包含

\overlay\GmsConfigOverlayCommon\res\values\config.xml
    <!-- For Factory Reset Protection -->
    <string name="config_persistentDataPackageName" translatable="false">com.google.android.gms</string>
2.vendor\google\products\gms_overlay_cn：不包含

解决方案

[VTS11R1]vts_kernel_encryption_test FBEPolicyTest#TestAesPerFileKeysPolicy

问题描述

vts_kernel_encryption_test
vts_kernel_encryption_test FBEPolicyTest#TestAesPerFileKeysPolicy
FAILURE:
[  INFO ] test/vts-testcase/kernel/encryption/utils.cpp:210:: /dev/block/platform/bootdevice/by-name/userdata is not a device-mapper device; metadata encryption is disabled
[  INFO ] test/vts-testcase/kernel/encryption/utils.cpp:265:: /dev/block/platform/bootdevice/by-name/userdata is mounted on /data with type ext4; UUID is 1bcf32795ea347bab94ae54d0cefd86c, raw block device is /dev/block/platform/bootdevice/by-name/userdata
[  INFO ] test/vts-testcase/kernel/encryption/file_based_encryption_tests.cpp:431:: Adding fscrypt master key, flags are 0x0, raw bytes are 67c6697351ff4aec29cdbaabf2fbe3467cc254f81be8e78d765a2e63339fc99a66320db73158a35a255d051758e95ed4abb2cdc69bb454110e827441213ddc87
[  INFO ] test/vts-testcase/kernel/encryption/file_based_encryption_tests.cpp:448:: Master key identifier is 9a281f7b673e99788e6caa93e612ec4b
[  INFO ] test/vts-testcase/kernel/encryption/file_based_encryption_tests.cpp:618:: Derived subkey 9a281f7b673e99788e6caa93e612ec4b using HKDF info 667363727970740001
[  INFO ] test/vts-testcase/kernel/encryption/file_based_encryption_tests.cpp:531:: Setting encryption policy on /data/unencrypted/vts-test-dir
[  INFO ] test/vts-testcase/kernel/encryption/file_based_encryption_tests.cpp:317:: Creating test file /data/unencrypted/vts-test-dir/file containing 1048576 bytes of data
[  INFO ] test/vts-testcase/kernel/encryption/file_based_encryption_tests.cpp:330:: Reading the raw ciphertext of /data/unencrypted/vts-test-dir/file from disk
[  INFO ] test/vts-testcase/kernel/encryption/file_based_encryption_tests.cpp:277:: Extent 1 of 1 is logical offset 0, physical offset 24117248, length 1048576, flags 0x1
[  INFO ] test/vts-testcase/kernel/encryption/file_based_encryption_tests.cpp:592:: Inode number: 917516
[  INFO ] test/vts-testcase/kernel/encryption/file_based_encryption_tests.cpp:600:: File nonce: 5b9443b10900d00691acad71a9c10a4a
[  INFO ] test/vts-testcase/kernel/encryption/file_based_encryption_tests.cpp:618:: Derived subkey e6387290d70f19f05482c3c6890052335aa8a52719df2ebc0183cdc40663d412c12db1344aba1dbf16c9c03773f9294b434660bd9b18a76a4c5d6b3d0592ae19 using HKDF info 6673637279707400025b9443b10900d00691acad71a9c10a4a
[  INFO ] test/vts-testcase/kernel/encryption/file_based_encryption_tests.cpp:704:: Verifying correctness of encrypted data
test/vts-testcase/kernel/encryption/file_based_encryption_tests.cpp:722: Failure
Expected equality of these values:
file_info.actual_ciphertext
Which is: { '5' (53, 0x35), 'n' (110, 0x6E), '\xDA' (218), '\x83' (131), '\xAE' (174), '\xAD' (173), 'x' (120, 0x78), '\x1B' (27), '\xC8' (200), '>' (62, 0x3E), '\x13' (19), '_' (95, 0x5F), 'o' (111, 0x6F), '\x87' (135), '\x16' (22), '\x98' (152), 'M' (77, 0x4D), '\xBD' (189), '\xA3' (163), '\xF' (15), '\xE' (14), '\xF1' (241), '\xB0' (176), '+' (43, 0x2B), '\x91' (145), 'B' (66, 0x42), '\xCC' (204), '\xC4' (196), '\xF' (15), 'A' (65, 0x41), '\xBD' (189), '\xD8' (216), ... }
computed_ciphertext
Which is: { '5' (53, 0x35), 'n' (110, 0x6E), '\xDA' (218), '\x83' (131), '\xAE' (174), '\xAD' (173), 'x' (120, 0x78), '\x1B' (27), '\xC8' (200), '>' (62, 0x3E), '\x13' (19), '_' (95, 0x5F), 'o' (111, 0x6F), '\x87' (135), '\x16' (22), '\x98' (152), 'M' (77, 0x4D), '\xBD' (189), '\xA3' (163), '\xF' (15), '\xE' (14), '\xF1' (241), '\xB0' (176), '+' (43, 0x2B), '\x91' (145), 'B' (66, 0x42), '\xCC' (204), '\xC4' (196), '\xF' (15), 'A' (65, 0x41), '\xBD' (189), '\xD8' (216), ... }

[CTS11R1]CtsMediaTestCases fail

问题描述

CtsMediaTestCases
android.media.cts.DecoderTest#testCodecResetsVP9WithSurface
android.media.cts.AdaptivePlaybackTest#testVP9_adaptiveReconfigDrc
android.media.cts.AdaptivePlaybackTest#testVP9_flushConfigureDrc
android.media.cts.AdaptivePlaybackTest#testVP9_adaptiveSmallReconfigDrc
android.media.cts.DecoderTest#testCodecResetsVP9WithoutSurface
FAILURE: android.media.MediaCodec$CodecException: Error 0x80001001

[STS-R-202010]CtsSecurityTestCases#android.security.cts.StagefrightTest#testStagefright_bug_65717533

问题描述

CtsSecurityTestCases

android.security.cts.StagefrightTest#testStagefright_bug_65717533
FAILURE: org.junit.runners.model.TestTimedOutException: test timed out after 900000 milliseconds

[CTS10R4/CTS11R1]android.security.cts.StagefrightTest#testStagefright_bug_37079296 fail

问题描述

CtsSecurityTestCases
android.security.cts.StagefrightTest#testStagefright_bug_37079296
Fail:
junit.framework.AssertionFailedError: Device *IS* vulnerable to BUG-37079296

解决方案

[STS_8.1-202009] RuntimeException in android.appsecurity.cts.AppSecurityTests#testPermissionDiffCert

Background

Broadcast timeout happens in customer MT6580 projects. Reproducing ratio = 100%.

It’s OK in customer MT6739 projects.

Not reproduced in Mediatek internal projects.

 

Testing Condition
STS Tool Version: 8.1-202009/6731883

TestCase: CtsAppSecurityHostTestCases

Fail Type: android.appsecurity.cts.AppSecurityTests#testPermissionDiffCert fail

继续阅读“[STS_8.1-202009] RuntimeException in android.appsecurity.cts.AppSecurityTests#testPermissionDiffCert”

[CTS11R1]android.appsecurity.cts.ApexSignatureVerificationTest#testApexPubKeyIsNotWellKnownKey fail

问题描述

 CtsAppSecurityHostTestCases  android.appsecurity.cts.ApexSignatureVerificationTest#testApexPubKeyIsNotWellKnownKey
Fail:
MultipleFailureException, There were 3 errors:
  java.lang.AssertionError: must not use well known pubkey
Expected: must not match well known key
     but: was </tmp/ApexSignatureVerificationTest5637729639613257975/tests-apex_com.android.i18n6068752760150743393/apex_pubkey>

apex_com.android.i18n

com.android.runtime

com.android.art

apex使用了google默认签名， 所以导致测试Fail.

解决方案

[VTS10.0r1]VtsKernelNetdTest#NetdSELinuxTest.CheckProperMTULabels_32bit fail

问题描述

VtsKernelNetdTest#NetdSELinuxTest.CheckProperMTULabels_32bit fail
VtsKernelNetdTest#NetdSELinuxTest.CheckProperMTULabels_64bit fail
system/netd/tests/netd_test.cpp:34
Expected equality of these values:
((1) &lt;&lt; 8 | (0))
Which is: 256
system("ls -Z /sys/class/net/*/mtu | egrep -q -v " "'^u:object_r:sysfs_net:s0 /sys/class/net/'")
Which is: 0

[STS10-202009]android.appsecurity.cts.LocationPolicyTest#testLocationPolicyPermissions Fail

问题描述

CtsAppSecurityHostTestCases
android.appsecurity.cts.LocationPolicyTest#testLocationPolicyPermissions
Fail:
java.lang.AssertionError: on-device tests failed:
android.appsecurity.cts.locationpolicy.LocationPolicyTest#testLocationPolicyPermissions:
java.lang.AssertionError: ACCESS_FINE_LOCATION and ACCESS_COARSE_LOCATION Permissions not granted. Should have received a security exception when invoking getCellLocation().