cts 测试:testFlashTurnOff fail

问题描述

cts测试中遇到testFlashTurnOff fail .
err log:
java.lang.Exception: There were 4 errors: java.lang.Throwable(Test failed for camera 0: Invalid state 3 not in expected list[4, 2] (expected = -1, actual = -1) ) java.lang.Throwable(Test failed for camera 0: state 3 index -1 is expected to be >= 0: (expected = 0 was not greater than actual = -1) )
该项测试要求:
flash从on->off的状态是[4,2],
从off->on(flash_mode_torch下发之前),flash的状态要求是[2,4]
从off->on的状态是[4,3]
而在测试过程中因为开关灯延迟的原因,导致AP 拿到的flash state 不符合预期。

解决方案

继续阅读“cts 测试:testFlashTurnOff fail”

[CTS10R3]CtsWindowManagerDeviceTestCases

问题描述

CtsWindowManagerDeviceTestCases

android.server.wm.ActivityManagerGetConfigTests#testDeviceConfig
android.server.wm.ActivityManagerGetConfigTests#testDeviceConfigWithSecondaryDisplay
Fail:

java.lang.AssertionError: Expected number of locales does not match expected:<1> but was:<0>
java.lang.AssertionError: Expected number of locales does not match expected:<1> but was:<0>

解决方案

继续阅读“[CTS10R3]CtsWindowManagerDeviceTestCases”

[STS9.0-4月]android.security.cts.AssetManagerTest#testCloseThenFinalize fail

问题描述

CtsSecurityTestCases
android.security.cts.AssetManagerTest#testCloseThenFinalize
Test failed to run to completion. Reason: 'Instrumentation run failed due to 'Process crashed.''. Check device logcat for details
android.security.cts.ActivityManagerTest#testActivityManager_attachNullApplication
Fail Details:Test failed to run to completion. Reason: 'Failed to receive adb shell test output within 990000 ms. Test may have timed out, or adb connection to device became unresponsive'. Check device logcat for details

[VTS10R3]android.hardware.neuralnetworks@1.1::IDevice not available

问题描述

VtsTrebleVendorVintfTes
VtsTrebleVendorVintfTest#DeviceManifest/SingleManifestTest.HalsAreServed/0_64bit fail:
test/vts-testcase/hal/treble/vintf/SingleManifestTest.cpp:51
Failed
android.hardware.neuralnetworks@1.1::IDevice not available.
04-14 14:59:03.504 ERROR 1 disallowed dependencies:
/vendor/bin/hw/android.hardware.neuralnetworks@1.1-service-gpunn: libcompiler_rt.so
04-14 14:59:03.505 ERROR 1 != 0 Total number of errors: 1
04-14 14:59:03.506 ERROR [Test Case] 1/1 testElfDependency FAIL

解决方案

继续阅读“[VTS10R3]android.hardware.neuralnetworks@1.1::IDevice not available”

[CTS10R3]CtsVideoTestCases fail

问题描述

CtsVideoTestCases
android.video.cts.VideoEncoderDecoderTest#testAvcOther0Perf0320x0240
fail
junit.framework.AssertionFailedError: Expected achievable frame rates forOMX.MTK.VIDEO.ENCODER.AVC video/avc 320x240: [161.0, 561.0].
android.video.cts.VideoEncoderDecoderTest#testAvcOther0Perf0720x0480
fail
junit.framework.AssertionFailedError: Expected achievable frame rates for OMX.MTK.VIDEO.ENCODER.AVC video/avc 720x480: [67.0, 234.0].
android.video.cts.VideoEncoderDecoderTest#testAvcOther0Perf1280x0720
fail
junit.framework.AssertionFailedError: Expected achievable frame rates for OMX.MTK.VIDEO.ENCODER.AVC video/avc 1280x720: [29.0, 102.0].
android.video.cts.VideoEncoderDecoderTest#testAvcOther0Perf1920x1080
fail
junit.framework.AssertionFailedError: Expected achievable frame rates for OMX.MTK.VIDEO.ENCODER.AVC video/avc 1920x1080: [29.0, 102.0].android.media.cts.VideoDecoderPerfTest#testVp8Goog0Perf1920x1080

android.video.cts.VideoEncoderDecoderTest#testAvcGoog0Perf0720x0480
Fail:
junit.framework.AssertionFailedError: Expected achievable frame rates for c2.android.avc.encoder video/avc 720x480: [45.0, 156.0].
Measured frame rate: [31.523520894659264, 29.52814031772279].
at junit.framework.Assert.fail(Assert.java:50)
at junit.framework.Assert.assertTrue(Assert.java:20)
at junit.framework.Assert.assertNull(Assert.java:237)
at android.video.cts.VideoEncoderDecoderTest.doTest(VideoEncoderDecoderTest.java:844)
at android.video.cts.VideoEncoderDecoderTest.perf(VideoEncoderDecoderTest.java:206)
at android.video.cts.VideoEncoderDecoderTest.testAvcGoog0Perf0720x0480(VideoEncoderDecoderTest.java:243)
XML 提供的 google avc codec framerate range 不符合 CTS 預期

解决方案

继续阅读“[CTS10R3]CtsVideoTestCases fail”

[CTS10R3]android.media.cts.ImageReaderDecoderTest#testGoogH264Image

问题描述

CtsMediaTestCases
android.media.cts.ImageReaderDecoderTest#testGoogH264Image
android.media.cts.ImageReaderDecoderTest#testGoogH264ImageReader
android.media.cts.ImageReaderDecoderTest#testGoogH265Image
android.media.cts.ImageReaderDecoderTest#testGoogH265ImageReader
Fail:

 java.lang.RuntimeException: while c2.android.avc.decoder decoding swirl_132x130_h264: {color-format=2135033992, track-id=1, level=256, mime=video/avc, frame-count=31, profile=65536, language=und, display-width=132, csd-1=java.nio.HeapByteBuffer[pos=0 lim=9 cap=9], durationUs=2583333, display-height=130, width=132, max-input-size=1597, frame-rate=12, height=130, csd-0=java.nio.HeapByteBuffer[pos=0 lim=28 cap=28]}

解决方案

继续阅读“[CTS10R3]android.media.cts.ImageReaderDecoderTest#testGoogH264Image”

[VTS-Q]刷GSI提示空间不足

问题描述

 烧录GSI,执行fastboot flash system system.img时,提示Resizing 'system' FAILED (remote: 'Not enough space to resize partition')。
在项目的BoardConfig.mk里定义了BOARD_MTK_SUPER_SIZE_KB:=2560000 , BOARD_MTK_SYSTEM_SIZE_KB:=1258292,但实际system.img只有600多M。
adb shell lpdump -j ,打印如下:
...
{
"name": "system",
"group_name": "main",
"is_dynamic": true,
"size": "630095872",
"fs_size": "619220992",
"fs_used": "619220992"
},
...
"block_devices": [
{
"name": "super",
"size": "2625634304",
"block_size": "4096",
"alignment": "1048576"
}
]
super空间充足,无法烧录gsi

解决方案

继续阅读“[VTS-Q]刷GSI提示空间不足”

[VTS10R3]VtsHalDrmV1_2Target

问题描述

VtsHalDrmV1_2Target
VtsHalDrmV1_2Target#DrmHalTestVendor/DrmHalTest.DoProvisioning/0_64bit
VtsHalDrmV1_2Target#DrmHalTestVendor/DrmHalTest.DoProvisioning/0_32bit
 VtsHalDrmV1_2Target#DrmHalTestVendor/DrmHalTest.DoProvisioning fail on widevine L1
 hardware/interfaces/drm/1.2/vts/functional/drm_hal_common.cpp:238

Expected equality of these values:

StatusV1_0::OK

Which is: 4-byte object <00-00 00-00>

status

Which is: 4-byte object <03-00 00-00>

[  FAILED  ] DrmHalTestVendor/DrmHalTest.DoProvisioning/0, where GetParam() = "/data/local/tmp/64/lib/libvtswidevine.so" (3498 ms)

解决方案

继续阅读“[VTS10R3]VtsHalDrmV1_2Target”

[CTS10R3]android.hardware.camera2.cts.ExtendedCameraCharacteristicsTest#testRecommendedStreamConfigurations fail

问题描述

CtsCameraTestCases
android.hardware.camera2.cts.ExtendedCameraCharacteristicsTest#testRecommendedStreamConfigurations fail
junit.framework.AssertionFailedError: No valid YUV_420_888 and PRIVATE preview formats found in recommended preview configuration for ID: 0
at junit.framework.Assert.fail(Assert.java:50)
at junit.framework.Assert.assertTrue(Assert.java:20)
at android.hardware.camera2.cts.ExtendedCameraCharacteristicsTest.verifyRecommendedPreviewConfiguration(ExtendedCameraCharacteristicsTest.java:504)
at android.hardware.camera2.cts.ExtendedCameraCharacteristicsTest.testRecommendedStreamConfigurations(ExtendedCameraCharacteristicsTest.java:834)
at java.lang.reflect.Method.invoke(Native Method)
at junit.framework.TestCase.runTest(TestCase.java:168)
at junit.framework.TestCase.runBare(TestCase.java:134)
at junit.framework.TestResult$1.protect(TestResult.java:115)
at androidx.test.internal.runner.junit3.AndroidTestResult.runProtected(AndroidTestResult.java:73)
at junit.framework.TestResult.run(TestResult.java:118)
at androidx.test.internal.runner.junit3.AndroidTestResult.run(AndroidTestResult.java:51)
at junit.framework.TestCase.run(TestCase.java:124)
at androidx.test.internal.runner.junit3.NonLeakyTestSuite$NonLeakyTest.run(NonLeakyTestSuite.java:62)
at androidx.test.internal.runner.junit3.AndroidTestSuite$2.run(AndroidTestSuite.java:101)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:462)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)
at java.lang.Thread.run(Thread.java:919)

解决方案

继续阅读“[CTS10R3]android.hardware.camera2.cts.ExtendedCameraCharacteristicsTest#testRecommendedStreamConfigurations fail”

How to fix SELinuxHostTest#testNoBugreportDenials fail

问题描述

 收到CTS 测试fail报告,如:
Module Passed Failed Assumption Failure Ignored Total Tests Done
armeabi-v7a CtsSecurityHostTestCases 0 1 0 0 1 true


armeabi-v7a CtsSecurityHostTestCases
Test Result Details
android.security.cts.SELinuxHostTest#testNoBugreportDenials
fail
junit.framework.AssertionFailedError: Found illegal SELinux denial(s): avc: denied { getattr } for path="/mnt/expand" dev="tmpfs" ino=1586 scontext=u:r:dumpstate:s0 tcontext=u:object_r:mnt_expand_file:s0 tclass=dir permissive=0
这是因为从Android Q开始 Google 新增了对dumpstate denials 的检查(AOSP/667966, AOSP/742461), 如果在执行Bugreport命令后,有出现dumpstate 的avc denied log,该测项就会fail.
 
Add CTS test to ensure bugreports don't generate SELinux denials.

This test takes a bugreport on the device and ensures that it does not
generate any dumpstate-related denials.
 
/cts/hostsidetests/security/src/android/cts/security/SELinuxHostTest.java
953   public void testNoBugreportDenials() throws Exception {
954   // Take a bugreport and get its logcat output.
955   mDevice.executeAdbCommand("logcat", "-c");
956   mDevice.getBugreport();
957   String log = mDevice.executeAdbCommand("logcat", "-d");
958   // Find all the dumpstate-related types and make a regex that will match them.
959   Set types = sepolicyAnalyzeGetTypesAssociatedWithAttribute("hal_dumpstate_server");
960   types.add("dumpstate");
961   String typeRegex = types.stream().collect(Collectors.joining("|"));
962   Pattern p = Pattern.compile("avc: *denied.*scontext=u:(?:r|object_r):(?:" + typeRegex + "):s0.*");
963   // Fail if logcat contains such a denial.
964   Matcher m = p.matcher(log);
965   StringBuilder errorString = new StringBuilder();
966   while (m.find()) {
967   errorString.append(m.group());
968   errorString.append("\n");
969   }
970   assertTrue("Found illegal SELinux denial(s): " + errorString, errorString.length() == 0);
971   }
 
dumpstate 作为AOSP自带的process,我们一般不会改到它的源码。此类问题的出现,一般是因为新增了一些目录/文件,而没有给dumpstate添加allow rules 或者dontaudit rules, 操作有被触发时就会出现avc denied log,引起测项fail。

解决方案

继续阅读“How to fix SELinuxHostTest#testNoBugreportDenials fail”

[VTSR3]vendor.mediatek.hardware.presence@1.0::IPresence not available.

问题描述

04-03 12:55:16 I/ModuleListener: [9/9] VtsTrebleVendorVintfTest#DeviceManifest/SingleManifestTest.InterfacesAreReleased/0_32bit fail:
test/vts-testcase/hal/treble/vintf/SingleManifestTest.cpp:51
Failed
vendor.mediatek.hardware.presence@1.0::IPresence not available.
test/vts-testcase/hal/treble/vintf/SingleManifestTest.cpp:51
Failed
vendor.mediatek.hardware.presence@1.0::IPresence not available.

解决方案

继续阅读“[VTSR3]vendor.mediatek.hardware.presence@1.0::IPresence not available.”

[VTS10R3]VtsFastbootVerification

问题描述

VtsFastbootVerification
VtsFastbootVerification#testFastbootReboot fail:
VtsFastbootVerification#testFastbootdSlotOperations
VtsFastbootVerification#testLogicalPartitionCommands
VtsFastbootVerification#testLogicalPartitionFlashing
Unknown error: test case requested but not executed.

解决方案

继续阅读“[VTS10R3]VtsFastbootVerification”

[CTSVR3][its test][scene3][camera1]scene3/test_3a_consistency FAIL

问题描述

 [its test][scene3][camera1]scene3/test_3a_consistency FAIL

该题原因是AE init清空m_u4Hbinwidth、m_u4Hbinheight再赋值的过程中,上层下了setAEMeteringArea(),m_u4Hbinwidth、m_u4Hbinheight为0导致Area计算错误,最终AE收敛发生变化的问题。

Its LOG一般可以看到三次的曝光设定差异太大导致的fail:

继续阅读“[CTSVR3][its test][scene3][camera1]scene3/test_3a_consistency FAIL”

[CTSV10R1]USB Audio Peripheral Attributes Test fail

问题描述

Audio Peripheral Attributes Test
通过OTG连接audio box,提示属性不匹配
Fail:
03-23 11:51:37.274 516 1447 D modules.usbaudio.audio_hal: usb:audio_hal::device_get_parameters() keys:sup_formats
03-23 11:51:37.274 516 1447 D modules.usbaudio.audio_hal: [USB_AUD] USB Name: 1 [VSL ]: USB-Audio - AudioBox 22 VSL, open path proc/asound/cards , isCTSDevice : 0, CTSkeyword:

解决方案

继续阅读“[CTSV10R1]USB Audio Peripheral Attributes Test fail”

[VTS10R3]VideoEncHidlTest.EncodeTestBufferMetaModes_OMX.google.h264.encoder_video_encoder.avc(default)_32bit fail

问题描述

VtsHalMediaOmxV1_0Host
VtsHalMediaOmxV1_0Host#VideoEncHidlTest.EncodeTestBufferMetaModes_OMX.google.h264.encoder_video_encoder.avc(default)_32bit
Fail:
hardware/interfaces/media/omx/1.0/vts/functional/common/media_hidl_test_common.cpp:749
Value of: false
  Actual: false
Expected: true
hardware/interfaces/media/omx/1.0/vts/functional/video/VtsHalMediaOmxV1_0TargetVideoEncTest.cpp:1446
Expected: testEOS(omxNode, observer, &iBuffer, &oBuffer, false, eosFlag) doesn't generate new fatal failures in the current thread.
  Actual: it does.

解决方案

继续阅读“[VTS10R3]VideoEncHidlTest.EncodeTestBufferMetaModes_OMX.google.h264.encoder_video_encoder.avc(default)_32bit fail”

[VTS10R3][kernel3.18]VtsKernelNetTest failed

问题描述

VtsKernelNetTest failed
VtsKernelNetTest#testKernelNetworking
failed traceback :

ERROR: testUpdateActiveSaMarks (xfrm_test.XfrmOutputMarkTest)

Test that the OUTPUT_MARK can be updated on an ACTIVE SA.

----------------------------------------------------------------------

Traceback (most recent call last):

File "/data/nativetest64/kernel_net_tests/kernel_net_tests/xfrm_test.py", line 833, in testUpdateActiveSaMarks

outNoStateCount = self.getXfrmStat(XFRM_STATS_OUT_NO_STATES);

File "/data/nativetest64/kernel_net_tests/kernel_net_tests/xfrm_test.py", line 806, in getXfrmStat

with open(XFRM_STATS_PROCFILE, 'r') as f:

IOError: [Errno 2] No such file or directory: '/proc/net/xfrm_stat'

解决方案

继续阅读“[VTS10R3][kernel3.18]VtsKernelNetTest failed”

[CTS10.0r1]CtsTelephonySdk28TestCases android.telephony.sdk28.cts.CellInfoTest#testCellInfoSdk28 fail

问题描述

android.telephony.sdk28.cts.CellInfoTest#testCellInfoSdk28 fail
java.lang.AssertionError: TelephonyManager.getAllCellInfo() returned an empty list

解决方案

继续阅读“[CTS10.0r1]CtsTelephonySdk28TestCases android.telephony.sdk28.cts.CellInfoTest#testCellInfoSdk28 fail”

[VTS10R3]VtsHalKeymasterV4_0Target

问题描述

VtsHalKeymasterV4_0Target
VtsHalKeymasterV4_0Target#ImportWrappedKeyTest.Success(default)_32bit
VtsHalKeymasterV4_0Target#ImportWrappedKeyTest.SuccessMasked(default)_32bit
VtsHalKeymasterV4_0Target#ImportWrappedKeyTest.WrongMask(default)_32bit
Fail1:
java.security.KeyStoreException: Failed to import wrapped key. Keystore error code: -13
Fail2:
hardware/interfaces/keymaster/4.0/vts/functional/keymaster_hidl_hal_test.cpp:2313
Expected equality of these values:
  ErrorCode::VERIFICATION_FAILED
    Which is: 4-byte object <E2-FF FF-FF>
  ImportWrappedKey( wrapped_key_masked, wrapping_key, wrapping_key_desc, zero_masking_key, AuthorizationSetBuilder() .Digest(Digest::SHA_2_256) .Padding(PaddingMode::RSA_OAEP))
    Which is: 4-byte object <F3-FF FF-FF>

解决方案

继续阅读“[VTS10R3]VtsHalKeymasterV4_0Target”