CTS问题分析4拓展-无法抓取tombstone的原因 | weiinter105

前面说到,在bionic/linker客户端以及system/core/dubuggerd服务端之间都加了相关的SIGSYS信号量处理,但还是抓不出tombstone,现查看原因。

先说结论:由于设置了信号处理函数导致的问题

继续阅读“CTS问题分析4拓展-无法抓取tombstone的原因 | weiinter105”

CTS/GTS问题分析6 | weiinter105

遇到一个Android P相关的问题,和原来CTS/GTS 问题分析1的表现是一样的,但是将http://gerrit.pt.miui.com/#/c/387000/这个修复cp过来,发现不生效,仍然报错,因此记录一下

问题初探

测试命令: run gts -m GtsGmscoreHostTestCases -t com.google.android.gts.devicepolicy.managedprovisioning.DeviceOwnerProvisioningHostsideTest#testRequiredAppsInManagedDevice

报错堆栈:

继续阅读“CTS/GTS问题分析6 | weiinter105”

CTS/GTS问题分析5 | weiinter105

问题初探

测试命令:

run cts -m CtsDevicePolicyManagerTestCases -t com.android.cts.devicepolicy.MixedManagedProfileOwnerTestApi25#testResetPasswordFbe

错误有两种情况,一种是直接进入系统桌面,一种是起一个测试case中的空白activity,经过分析,两者都是同一个原因造成的。因此以任一种情况举例。报错堆栈如下:

继续阅读“CTS/GTS问题分析5 | weiinter105”

CTS/GTS问题分析4 | weiinter105

问题初探

测试命令:
run cts -m CtsOsTestCases -t android.os.cts.SeccompTest#testIsolatedServicePolicy

报错堆栈:
07-24 00:50:08.627 2633 4112 I ActivityManager: Process android.os.cts (pid 13402) has died: vis SF
07-24 00:50:08.627 2022 2022 I Zygote : Process 13402 exited due to signal (31)
07-24 00:50:08.627 13379 13399 I TestRunner: failed: testIsolatedServicePolicy(android.os.cts.SeccompTest)

继续阅读“CTS/GTS问题分析4 | weiinter105”

CTS/GTS问题分析3 | weiinter105

android.security.cts.ListeningPortsTest#testNoListeningLoopbackTcp6Ports
android.security.cts.ListeningPortsTest#testNoListeningLoopbackUdp6Ports
android.security.cts.ListeningPortsTest#testNoRemotelyAccessibleListeningUdp6Ports

问题分析

本地测了一下,前两条没问题,那么下面重点先说下第三条的分析流程:

测试命令: run sts-userbuild -m CtsSecurityTestCases -t android.security.cts.ListeningPortsTest#testNoRemotelyAccessibleListeningUdp6Ports

测试结果:

继续阅读“CTS/GTS问题分析3 | weiinter105”

CTS/GTS问题分析2 | weiinter105

问题初探

测试命令: run gts-suite -s ID -o -m GtsGmscoreHostTestCases -t com.google.android.gts.devicepolicy.managedprovisioning.DeviceOwnerProvisioningHostsideTest#testRequiredAppsInManagedProfileForManagedDevice

报错堆栈:
07-27 06:59:30.611 32075 32125 I SilentProvisioningTest: managedProfileProvisionedReceiver.awaitForBroadcast(): failed
07-27 06:59:30.612 2091 2129 D ContactsDatabaseHelper: insertMimeType: vnd.android.cursor.item/website

继续阅读“CTS/GTS问题分析2 | weiinter105”

CTS/GTS问题分析1 | weiinter105

问题初探

测试命令: run gts -m GtsGmscoreHostTestCases -t com.google.android.gts.devicepolicy.managedprovisioning.DeviceOwnerProvisioningHostsideTest#testRequiredAppsInManagedDevice

报错堆栈
07-18 16:53:12 I/XtsHostTestBase: Test com.google.android.gts.playstore.ResetPreferredAppsTest#testPersistDefaultBrowser: PASSED
07-18 16:53:19 I/XtsHostTestBase: Test com.google.android.gts.managedprovisioning.AfwRequiredAppsTest#testRequiredApps_DeviceOwner_withGms: FAILURE
07-18 16:53:19 W/XtsHostTestBase: junit.framework.AssertionFailedError: com.google.android.gms is not installed

继续阅读“CTS/GTS问题分析1 | weiinter105”

[CTS]CtsAppTestCases -t android.app.cts.SystemFeaturesTest#testCameraFeatures

问题描述


 这个会测试Device的一些feature,不同的device可能会配置不同的feature,比如flash,focus等项目,因此需要根据实际情况去配置
常见fail log的形式:
junit.framework.AssertionFailedError: PackageManager#hasSystemFeature should NOT return true for android.hardware.camera.xxxx
如:
junit.framework.AssertionFailedError: PackageManager#hasSystemFeature should NOT return true for android.hardware.camera.capability.raw

 

解决方案

继续阅读“[CTS]CtsAppTestCases -t android.app.cts.SystemFeaturesTest#testCameraFeatures”

[cts-on-gsi 8.1_R6/CTS8.1 R10] CtsAutoFillServiceTestCases android.autofillservice.cts.SessionLifecycleTest#testDatasetAuthResponseWhileAutofilledAppIsLifecycled 测试 fail

问题描述


  cts-on-gsi 8.1_R6 CtsAutoFillServiceTestCases android.autofillservice.cts.SessionLifecycleTest#testDatasetAuthResponseWhileAutofilledAppIsLifecycled 测试 fail
11-13 15:36:50 D/ModuleListener: ModuleListener.testFailed(android.autofillservice.cts.SessionLifecycleTest#testDatasetAuthResponseWhileAutofilledAppIsLifecycled, android.autofillservice.cts.RetryableException: Timedout out after 2000 ms

 

[CTS] android.cts.security.SELinuxNeverallowRulesTest#testNeverallowRules265

问题描述


 CtsSecurityHostTestCases
android.cts.security.SELinuxNeverallowRulesTest#testNeverallowRules265
fail
junit.framework.AssertionFailedError: The following errors were encountered when validating the SELinuxneverallow rule:

 

[CTS9.0-R3]CtsUsageStatsTestCases包下,五条case测试fail

问题描述


ndroid.app.usage.cts.NetworkUsageStatsTest#testAppDetails
fail junit.framework.AssertionFailedError: No Rx bytes usage for uid 10903 tag null state STATE_ALL
android.app.usage.cts.NetworkUsageStatsTest#testAppSummary
fail junit.framework.AssertionFailedError: No Rx bytes usage for uid 10903
android.app.usage.cts.NetworkUsageStatsTest#testTagDetails
fail junit.framework.AssertionFailedError: No Rx bytes tagged with 0xf00d for uid 10903
android.app.usage.cts.NetworkUsageStatsTest#testUidDetails
fail junit.framework.AssertionFailedError: No Rx bytes usage for uid 10903
android.app.usage.cts.NetworkUsageStatsTest#testUidTagStateDetails
fail junit.framework.AssertionFailedError: No Rx bytes usage for uid 10903 tag 0xf00d state STATE_FOREGROUND

解决方案

继续阅读“[CTS9.0-R3]CtsUsageStatsTestCases包下,五条case测试fail”

[CTS-8.1R10] android.content.pm.cts.shortcutmanager.ShortcutManagerFakingPublisherTest#testSpoofingPublisher

问题描述


[CTS-8.1R10] android.content.pm.cts.shortcutmanager.ShortcutManagerFakingPublisherTest#testSpoofingPublisher

junit.framework.AssertionFailedError: Expected exception type java.lang.SecurityException was not thrown

解决方案

继续阅读“[CTS-8.1R10] android.content.pm.cts.shortcutmanager.ShortcutManagerFakingPublisherTest#testSpoofingPublisher”