android.hardware.camera2.cts.RecordingTest#testBasicRecording

问题描述

CTS Test:testBasicRecordingCTS fail:Video duration doesn’t match: recorded 2619.000000ms, expected [4650.000000,4650.000000]ms.从fail的原因来看,是帧率过大导致的(一般此项fail原因都是帧率不够导致)

Log 分析:

继续阅读“android.hardware.camera2.cts.RecordingTest#testBasicRecording”

CTS8.1R13,R14测试CtsAppSecurityHostTestCases---android.appsecurity.cts.AppSecurityTests#testPermissionDiffCert失败

问题描述

 CTS8.1R13,R14测试CtsAppSecurityHostTestCases---android.appsecurity.cts.AppSecurityTests#testPermissionDiffCert失败
 对应的fail log为:

继续阅读“CTS8.1R13,R14测试CtsAppSecurityHostTestCases---android.appsecurity.cts.AppSecurityTests#testPermissionDiffCert失败”

【CTS】android.host.multiuser.CreateUsersNoAppCrashesTest#testCanCreateGuestUser 测试不过

问题描述

CMASReceiver出现crash
复现步骤:
1. 插卡打开手机.
2. 设置>> 系统 >> 多用户 >> 选择客人模式
4. 在客人模式执行多任务,使用信息应用
5. CMASReceiver出现crash

继续阅读“【CTS】android.host.multiuser.CreateUsersNoAppCrashesTest#testCanCreateGuestUser 测试不过”

GPS 周期翻转问题提醒

Reminder of GPS Week Number rollover issue

 

As we previously announced, the broadcast GPS Week Number will rollover from 1023 to 0 on April 6th, 2019. For those who have issues and cannot prepare a new bug fix build on time due to the build approval logistics, reach out to your Google contact. We will review and provide an exceptional build approval guidance only applicable for GPS Week Number rollover issue.

继续阅读“GPS 周期翻转问题提醒”

[cts9.0r6] android.jni.cts.JniStaticTest#test_linker_namespaces

问题描述

 [cts9.0 r6]
CtsJniTestCases
android.jni.cts.JniStaticTest#test_linker_namespaces
fail
 junit.framework.AssertionFailedError: The library “/vendor/lib/libMcClient.so” is a public library but it cannot be loaded: dlopen failed: library “/vendor/lib/libMcClient.so” not found

继续阅读“[cts9.0r6] android.jni.cts.JniStaticTest#test_linker_namespaces”

Google CTS 9.0_r6 CtsIncidentHostTestCases模块有四条case不过

问题描述

  Google CTS 9.0_r6 CtsIncidentHostTestCases模块有四条case不过
1.com.android.server.cts.AlarmManagerIncidentTest#testAlarmManagerServiceDump
2.com.android.server.cts.IncidentdTest#testIncidentReportDumpAuto
3.com.android.server.cts.IncidentdTest#testIncidentReportDumpExplicit
4.com.android.server.cts.IncidentdTest#testIncidentReportDumpLocal

继续阅读“Google CTS 9.0_r6 CtsIncidentHostTestCases模块有四条case不过”

CTS问题分析13-CTS问题分析10(续) | weiinter105

问题分析

这个问题不是第一次出现,详见CTS问题分析10;但当时有更紧急的问题,所以并没有继续深入分析,只是分析到持有大量的CompatibilityTestSuite导致retry时发生错误;

但是这次又出现了,因此有必要进行下调研,以确保下次不再复现此问题

retry 命令: run retry –retry 0 –shard-count 2 -s 7c6252f -s 7c62472

继续阅读“CTS问题分析13-CTS问题分析10(续) | weiinter105”

CTS/GTS/GSI/VTS无法提交报告问题复盘 | weiinter105

一.问题原因

这个问题是由于多个方面造成的,梳理下问题发生的流程

本次问题产生原因

1.首先这个是odm产生的问题,修改了修改model name不规范,只修改了system的属性,没有修改vendor下面的属性

2.odm的推送直接push到了dev上,但是有一条change又进了stable1x,dev上的默认被拉到了stable2x,但是gerrit上只有1x这个提交

3.士伟搜了gerrit上odm的修改,认为只进了1x,所以修复也只进了1x,注意对这个问题进行总结 (要不不进,要进进全)

4.打小数版时CTS测试没有按照上传报告失败问题总结进行检查,导致2x小数版没有发现该问题

5.整数包上传报告时暴露问题

继续阅读“CTS/GTS/GSI/VTS无法提交报告问题复盘 | weiinter105”

CTS9.0R6 造成3筆 location test cases: GNSS Measurement Before Location Test 、Measurement Values Test , testGnssStatusValues测试不通过

问题描述

 CTS9.0R6 造成3筆 location test cases: GNSS Measurement Before Location Test 、Measurement Values Test , testGnssStatusValues测试不通过

解决方案

继续阅读“CTS9.0R6 造成3筆 location test cases: GNSS Measurement Before Location Test 、Measurement Values Test , testGnssStatusValues测试不通过”

[CTS 9.0R5]com.android.cts.devicepolicy.MixedManagedProfileOwnerTest#testKeyManagement fail

问题描述

 com.android.cts.devicepolicy.MixedManagedProfileOwnerTest#testKeyManagement
fail
java.lang.AssertionError: On-device tests failed:

解决方案

继续阅读“[CTS 9.0R5]com.android.cts.devicepolicy.MixedManagedProfileOwnerTest#testKeyManagement fail”

[CTS 9.0R5]android.hardware.camera2.cts.StillCaptureTest#testAeCompensation fail

问题描述

 android.hardware.camera2.cts.StillCaptureTest#testAeCompensation fail:
java.lang.Exception: There were 8 errors:
java.lang.Throwable(Test failed for camera 0: Exposure compensation ratio exceeds error tolerence: expected(0.250000) observed(1.000000). Normal exposure time 49996 us, sensitivity 211. Compensated exposure time 49996 us, sensitivity 211, value 4.0 is out of range [0.8, 1.2])
java.lang.Throwable(Test failed for camera 0: Exposure compensation ratio exceeds error tolerence: expected(0.500000) observed(1.000000). Normal exposure time 49996 us, sensitivity 211. Compensated exposure time 49996 us, sensitivity 211, value 2.0 is out of range [0.8, 1.2])
java.lang.Throwable(Test failed for camera 0: Exposure compensation ratio exceeds error tolerence: expected(2.000000) observed(1.000000). Normal exposure time 49996 us, sensitivity 211. Compensated exposure time 49996 us, sensitivity 211, value 0.5 is out of range [0.8, 1.2])
java.lang.Throwable(Test failed for camera 0: Exposure compensation ratio exceeds error tolerence: expected(4.000000) observed(1.000000). Normal exposure time 49996 us, sensitivity 211. Compensated exposure time 49996 us, sensitivity 211, value 0.25 is out of range [0.8, 1.2])
java.lang.Throwable(Test failed for camera 1: Exposure compensation ratio exceeds error tolerence: expected(0.250000) observed(1.000000). Normal exposure time 20000 us, sensitivity 113. Compensated exposure time 20000 us, sensitivity 113, value 4.0 is out of range [0.8, 1.2])
java.lang.Throwable(Test failed for camera 1: Exposure compensation ratio exceeds error tolerence: expected(0.500000) observed(1.000000). Normal exposure time 20000 us, sensitivity 113. Compensated exposure time 20000 us, sensitivity 113, value 2.0 is out of range [0.8, 1.2])
java.lang.Throwable(Test failed for camera 1: Exposure compensation ratio exceeds error tolerence: expected(2.000000) observed(1.000000). Normal exposure time 20000 us, sensitivity 113. Compensated exposure time 20000 us, sensitivity 113, value 0.5 is out of range [0.8, 1.2])
java.lang.Throwable(Test failed for camera 1: Exposure compensation ratio exceeds error tolerence: expected(4.000000) observed(1.000000). Normal exposure time 20000 us, sensitivity 113. Compensated exposure time 20000 us, sensitivity 113, value 0.25 is out of range [0.8, 1.2])

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

[CTS 9.0R5]com.android.cts.devicepolicy.MixedManagedProfileOwnerTest#testKeyManagement fail

问题描述

 com.android.cts.devicepolicy.MixedManagedProfileOwnerTest#testKeyManagement
fail
java.lang.AssertionError: On-device tests failed:

继续阅读“[CTS 9.0R5]com.android.cts.devicepolicy.MixedManagedProfileOwnerTest#testKeyManagement fail”

CTS February releases are available

CTS February releases are available

The CTS February releases for Android 9.0, 8.1, 8.0, 7.1, and 7.0 are available on the Compatibility Test Suite Downloads page. These releases contain continuous improvements of tests and test infrastructure, and verify security patches up to January 2019 Public Security Bulletin.

For partners in China, the CTS packages can be downloaded from https://source.android.google.cn/ without using VPN for better reliability.

The details and delta from last release can be found in the following change lists:

继续阅读“CTS February releases are available”

【cts_P】CtsLibcoreTestCases libcore.libcore.icu.DateIntervalFormatTest#testEndAtMidnight

问题描述


run cts -m CtsLibcoreTestCases -t libcore.libcore.icu.DateIntervalFormatTest#testEndAtMidnight -o
 01-07 16:35:46 I/ModuleListener: [1/1] libcore.libcore.icu.DateIntervalFormatTest#testEndAtMidnight fail:
junit.framework.ComparisonFailure: expected:<February 27, []04:00 – 00:00> but was:<February 27, [2018, ]04:00 – 00:00>
at junit.framework.Assert.assertEquals(Assert.java:85)
at junit.framework.Assert.assertEquals(Assert.java:91)
at libcore.libcore.icu.DateIntervalFormatTest.testEndAtMidnight(DateIntervalFormatTest.java:442)
at java.lang.reflect.Method.invoke(Native Method)

 

设置Google Assistant 为默认的Assistant

问题描述


1.需求来源:
从2018年10月29日起,所有欧盟项目必须将Google设为默认的Assist应用, 对于非欧盟项目,运行Android 8.0或者更高版本的项目不管是初始送测版本还是维护版本,都需要将Google设为默认的Assist应用,具体执行的时间请看如下表格:

[CTS 8.1][VtsHalMediaOmxV1_0Host]FAIL 信息与OMX.MTK.AUDIO.DECODER.WMA_audio_decoder相关

问题描述


 CTS 和VTS mediatek相关测试,如果测试项目包含.OMX.MTK.AUDIO.DECODER.WMA_audio_decoder.wma相关信息引起的fail,
一般是由于客户没有拿到wma的licence,缺少相关的库而导致的失败;

 

解决方案

继续阅读“[CTS 8.1][VtsHalMediaOmxV1_0Host]FAIL 信息与OMX.MTK.AUDIO.DECODER.WMA_audio_decoder相关”