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 不符合预期。

解决方案

MainlineModule

问题描述

GtsOsTestCases
com.google.android.os.gts.MainlineModulePreloadTest
com.google.android.os.gts com.google.android.os.gts.MainlineConfigurationTest#testMainlineApprovedTrain

解决方案

Q1: Mainline release 是什麼? What is Mainline release?Ans: Google 列進 Mainline scope 的 module 會由 Google 出 prebuilt binary 並 release 給有 GMS license 的廠商, Android 10 要過 Google GMS 認證需要 preload Mainline release, 也就是要用 Google build 的 binary, 不能用客戶修改過、客戶自己用 AOSP build 出的 binary。

From Android 10, we need to preload Mainline release into our SW load to pass xTS to obtain GMS certification. It means Google will release prebuilt binary for modules in Mainline scope to Android partners who have GMS lincense and Android partners must use Google Mainline release and cannot use binaries built by Android partners.

继续阅读“MainlineModule”

SystemVendorTest#ServedHwbinderHalsAreInManifest fail

问题描述

[VTS][cts-on-gsi]
CtsOnGsiTrebleFrameworkVintfTest
SystemVendorTest#ServedHwbinderHalsAreInManifest fail
Fail:
test/vts-testcase/hal/treble/vintf/SystemVendorTest.cpp:78: Failure                                                                                                        Expected: (manifest_hwbinder_hals_.find(name)) != (manifest_hwbinder_hals_.end()), actual: 8-byte object <68-C8 6A-DD 7F-00 00-00> vs 8-byte object <68-C8 6A-DD 7F-00 00-00>

[VTS10R4]VtsKernelNetTest#testKernelNetworking fail

问题描述

VtsKernelNetTest
VtsKernelNetTest#testKernelNetworking
Fail:
testAddDelSa (pf_key_test.PfKeyTest) ... FAIL

FAIL: testAddDelSa (pf_key_test.PfKeyTest)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/data/nativetest64/kernel_net_tests/kernel_net_tests/pf_key_test.py", line 52, in testAddDelSa
    self.assertEquals(2, len(sainfos))
AssertionError: 2 != 12

[CTS9.0R13]CtsCameraTestCases fail

问题描述

CtsCameraTestCases
android.hardware.camera2.cts.RecordingTest#testBasicRecording
android.hardware.camera2.cts.RecordingTest#testRecordingFramerateLowToHigh
android.hardware.camera2.cts.RecordingTest#testBurstVideoSnapshot
android.hardware.camera2.cts.BurstCaptureTest#testYuvBurst
合入7月安全补丁导致 fail
Fail:
junit.framework.AssertionFailedError: Camera 0: Video duration doesn't match: recorded 3613.000000ms, expected [3003.000000,3003.000000]ms.
junit.framework.AssertionFailedError: Camera 0: Video frame drop rate too high: 9.859155%, tolerance 5.000000%. Video size: 3840x2160, expectedDuration [2666.666504,2666.666504], expectedFrameDuration 33.333332, frameDropCnt 7, frameCount 71
 junit.framework.AssertionFailedError: Camera 0: Video frame drop rate too high: 6.024096%, tolerance 5.000000%. Video size: 3840x2160, expectedDuration [2733.333252,2733.333252], expectedFrameDuration 33.333332, frameDropCnt 5, frameCount 83
junit.framework.AssertionFailedError: Cam 3: Burst frame duration mean 62401588.0 ns is larger than acceptable, expecting below 50000000 ns, allowing below 55000000
Line 77985: 01-01 02:17:56.552341   738 20835 W MDP     : DpIsp: 0xfb26a6c0, src 220 ms, 0, 0, 0, 0

解决方案

[CTS10R4]android.security.cts.StagefrightTest#testBug_67737022 fail

问题描述

CtsSecurityTestCases
android.security.cts.StagefrightTest#testBug_67737022
Fail:
Test failed to run to completion. Reason: 'Instrumentation run failed due to 'Process crashed.''. Check device logcat for details

[CTS10R4]android.security.cts.StagefrightTest#testStagefright_cve_2016_2454 fail

问题描述

CtsSecurityTestCases
android.security.cts.StagefrightTest#testStagefright_cve_2016_2454
Fail:
org.junit.runners.model.TestTimedOutException: test timed out after 900000 milliseconds

[STS10-06]android.security.cts.StagefrightTest#testStagefright_cve_2019_2334

问题描述

CtsSecurityTestCases
android.security.cts.StagefrightTest#testStagefright_cve_2019_2334
Fail:
org.junit.runners.model.TestTimedOutException: test timed out after 900000 milliseconds

CTS10R3/VTS 10R3][Q GO]android.media.cts.MediaCodecCapabilitiesTest#testGetMaxSupportedInstances fail

问题描述

[CTS/VTS 10R3][QGO/512M]
[CTS][cts-on-gsi]
CtsMediaTestCases
android.media.cts.MediaCodecCapabilitiesTest#testGetMaxSupportedInstance
junit.framework.AssertionFailedError: In order to pass the test, please publish following codecs' concurrent instances limit in /etc/media_codecs.xml:
<MediaCodec name="OMX.MTK.AUDIO.DECODER.MP3" type="audio/mpeg" >
    <Limit name="concurrent-instances" max="16" />
</MediaCodec>

[STS8.1]testStagefright_bug_110435401 and testStagefright_bug_68664359

问题描述

CtsSecurityTestCases
android.security.cts.StagefrightTest#testStagefright_bug_110435401
android.security.cts.StagefrightTest#testStagefright_bug_68664359
java.lang.AssertionError: operation not completed within timeout of 60000ms

继续阅读“[STS8.1]testStagefright_bug_110435401 and testStagefright_bug_68664359”

[VTS10R4]VtsHalWifiSupplicantV1_2Host

问题描述

VtsHalWifiSupplicantV1_2Host
VtsHalWifiSupplicantV1_2Host#SupplicantStaIfaceHidlTest.StartDppEnrolleeInitiator(default,default,default,default,default)_64bit
VtsHalWifiSupplicantV1_2Host#SupplicantStaIfaceHidlTest.StartDppConfiguratorInitiator(default,default,default,default,default)_64bit
VtsHalWifiSupplicantV1_2Host#SupplicantStaNetworkHidlTest.SetGetGroupMgmtCipher(default,default,default,default,default)_64bit
VtsHalWifiSupplicantV1_2Host#SupplicantStaNetworkHidlTest.EnableSuiteBEapOpenSslCiphers(default,default,default)_64bit
Fail:
hardware/interfaces/wifi/supplicant/1.2/vts/functional/supplicant_sta_iface_hidl_test.cpp:407
Expected equality of these values:
  std::cv_status::no_timeout
    Which is: 4-byte object <00-00 00-00>
  wait(SupplicantStaIfaceHidlTest::DppCallbackType::EVENT_FAILURE)
    Which is: 4-byte object <01-00 00-00>

继续阅读“[VTS10R4]VtsHalWifiSupplicantV1_2Host”

[STS11 R0-202007]android.security.sts.Poc18_06#testPocCVE_2018_9409 fail

问题描述

Suite / Build (R)11 202007StsHostTestCases

android.security.sts.Poc18_06#testPocCVE_2018_9409

Fail:

com.android.tradefed.device.DeviceUnresponsiveException: Attempted shell (vndservice) &gt; /dev/null 2&gt;&amp;1; echo $? multiple times on device 055552502L000912 without communication success. Aborting.

继续阅读“[STS11 R0-202007]android.security.sts.Poc18_06#testPocCVE_2018_9409 fail”

[CTS10R3][MT6771]android.video.cts.VideoEncoderDecoderTest#testAvcOther0Qual0320x0240 fail

问题描述

[CTS10R3][MT6771]
CtsVideoTestCases
android.video.cts.VideoEncoderDecoderTest#testAvcOther0Qual0320x0240
fail:
junit.framework.AssertionFailedError: rms error is bigger than the limit [1.705549439004595, 1.7481510867834686, 45.12865402872597, 45.55498948157783, 22.659392092463555, 12.045954830472251, 36.54067065917403, 21.267713558349428, 9.689990540071062, 6.778597281968527, 32.54079661662333, 9.445533041837525, 18.634087700889584, 6.7517520359944765, 20.300935747453178, 17.36366100029983, 46.599351736072705, 15.336949935803185, 17.07504797455437, 4.151855140911242] vs 20.0

這個是cache 機制差異的問題
6771 少了 HW access 後的invalidate ,這個測項後面接的是google SW codec 才會機率性fail

继续阅读“[CTS10R3][MT6771]android.video.cts.VideoEncoderDecoderTest#testAvcOther0Qual0320x0240 fail”

[CTS/VTS10R4]android.location.cts.GnssMeasurementValuesTest#testListenForGnssMeasurements

问题描述

CtsLocationTestCases
android.location.cts.GnssMeasurementValuesTest#testListenForGnssMeasurements
Fail:
junit.framework.AssertionFailedError: Failing tests are:
(Test: FAIL) Used Svs with no Meas: [GNSS_L1.5.19, GNSS_L1.1.3, GNSS_L1.3.2, GNSS_L1.5.1]

继续阅读“[CTS/VTS10R4]android.location.cts.GnssMeasurementValuesTest#testListenForGnssMeasurements”

[VTS10R3]VtsHalSensorsV2_0Target#SensorsHidlTest.FlushSensor(default)_32bit fail

问题描述

VtsHalSensorsV2_0Target
VtsHalSensorsV2_0Target#SensorsHidlTest.FlushSensor(default)_32bit
Fail:
hardware/interfaces/sensors/2.0/vts/functional/VtsHalSensorsV2_0TargetTest.cpp:730
Expected equality of these values:
  callback.getFlushCount(sensor.sensorHandle)
    Which is: 0
  expectedFlushCount
    Which is: 5

继续阅读“[VTS10R3]VtsHalSensorsV2_0Target#SensorsHidlTest.FlushSensor(default)_32bit fail”

[CTS10R3]android.hardware.camera2.cts.StillCaptureTest#testAeCompensation fail

问题描述

CtsCameraTestCases
android.hardware.camera2.cts.StillCaptureTest#testAeCompensation
Fail:
java.lang.Exception: There were 4 errors:
java.lang.Throwable(Test failed for camera 0: Exposure compensation ratio exceeds error tolerence: expected(0.015625) observed(0.061857). Normal exposure time 30000 us, sensitivity 431. Compensated exposure time 7271 us, sensitivity 110, value 3.958843000773395 is out of range [0.8, 1.2])
java.lang.Throwable(Test failed for camera 0: Exposure compensation ratio exceeds error tolerence: expected(0.031250) observed(0.062430). Normal exposure time 30000 us, sensitivity 493. Compensated exposure time 8394 us, sensitivity 110, value 1.997760649087221 is out of range [0.8, 1.2])
java.lang.Throwable(Test failed for camera 0: Exposure compensation ratio exceeds error tolerence: expected(32.000000) observed(15.938196). Normal exposure time 30000 us, sensitivity 455. Compensated exposure time 59999 us, sensitivity 3626, value 0.49806862179487177 is out of range [0.8, 1.2])
java.lang.Throwable(Test failed for camera 0: Exposure compensation ratio exceeds error tolerence: expected(64.000000) observed(16.076068). Normal exposure time 30000 us, sensitivity 524. Compensated exposure time 59999 us, sensitivity 4212, value 0.25118856154580155 is out of range [0.8, 1.2])

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

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 &gt;= 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