androdi 9.0 P版本 CTS 常见问题表格
16lz
2021-12-04
| 测试项目 | 结果 | 详细原因 | 解决方案 |
| arm64-v8a CtsAccessibilityServiceTestCases | |||
| Test | Result | Details | |
| android.accessibilityservice.cts.AccessibilityGestureDispatchTest#testAngledPinch_looksReasonable | fail | junit.framework.AssertionFailedError: Did not receive required events. Got: | 复测pass |
| android.accessibilityservice.cts.AccessibilityGestureDispatchTest#testContinuedGesture_withLineDisconnect_isCancelled | fail | junit.framework.AssertionFailedError: Did not receive required events. Got: | 复测pass |
| android.accessibilityservice.cts.AccessibilityGestureDispatchTest#testContinuedGestures_motionEventsContinue | fail | junit.framework.AssertionFailedError: Did not receive required events. Got: | 复测pass |
| android.accessibilityservice.cts.AccessibilityGestureDispatchTest#testLongClickAt_producesEventsWithLongClickTiming | fail | junit.framework.AssertionFailedError: Did not receive required events. Got: | 复测pass |
| android.accessibilityservice.cts.AccessibilityGestureDispatchTest#testSlowSwipe_shouldNotContainMovesForTinyMovement | fail | junit.framework.AssertionFailedError: Did not receive required events. Got: | 复测pass |
| android.accessibilityservice.cts.AccessibilityGestureDispatchTest#testSwipe_shouldContainPointsInALine | fail | junit.framework.AssertionFailedError: Did not receive required events. Got: | 复测pass |
| arm64-v8a CtsActivityManagerDeviceTestCases | |||
| Test | Result | Details | |
| android.server.am.SplashscreenTests#testSplashscreenContent | fail | java.lang.AssertionError: More than 2.0% of pixels have wrong color primaryPixels=253799 secondaryPixels=0 wrongPixels=104281 | 复测pass,已修改,测试pass。驱动修改分辨率解决。硬件规格480*800，驱动设置成480*854，修改和硬件规格一样解决。 |
| arm64-v8a CtsAppSecurityHostTestCases | |||
| Test | Result | Details | |
| android.appsecurity.cts.DocumentsTest#testCreateDocumentAtInitialLocation | fail | java.lang.AssertionError: on-device tests failed: | 复测pass |
| android.appsecurity.cts.DocumentsTest#testCreateNew | fail | java.lang.AssertionError: on-device tests failed: | 复测pass |
| android.appsecurity.cts.DocumentsTest#testOpenDocumentAtInitialLocation | fail | java.lang.AssertionError: on-device tests failed: | 复测pass |
| android.appsecurity.cts.DocumentsTest#testOpenDocumentTreeAtInitialLocation | fail | java.lang.AssertionError: on-device tests failed: | 复测pass |
| android.appsecurity.cts.DocumentsTest#testOpenSimple | fail | java.lang.AssertionError: on-device tests failed: | 复测pass |
| android.appsecurity.cts.DocumentsTest#testOpenVirtual | fail | java.lang.AssertionError: on-device tests failed: | 复测pass |
| arm64-v8a CtsAutoFillServiceTestCases | |||
| Test | Result | Details | |
| android.autofillservice.cts.MultiWindowLoginActivityTest#testSplitWindow | fail | android.autofillservice.cts.RetryableException: waitForObject(BySelector [RES='\Qandroid:id/autofill_dataset_picker\E']) (timeout=UI_DATASET_PICKER_TIMEOUT: [current=10000ms; multiplier=2.0x; max=10000ms]) | 复测pass |
| android.autofillservice.cts.SimpleSaveActivityTest#testDismissSave_byTouchingOutside | fail | java.lang.AssertionError: Should not be showing save UI for type 0 after 5000ms, but got [Save to InstrumentedAutoFillService?, NO THANKS, SAVE] | 复测pass |
| arm64-v8a CtsCameraTestCases | |||
| Test | Result | Details | |
| android.hardware.camera2.cts.CaptureRequestTest#testFocusDistanceControl | fail | java.lang.Exception: There were 4 errors: | 复测pass，驱动修改效果参数，MinFocusDistance 之后复测pass |
| arm64-v8a CtsCarrierApiTestCases | |||
| Test | Result | Details | |
| android.carrierapi.cts.ApnDatabaseTest#testDeleteConflictCase | fail | java.lang.AssertionError: This test requires a SIM card with carrier privilege rule on it. | 特殊SIM卡 |
| android.carrierapi.cts.ApnDatabaseTest#testQueryConflictCase | fail | java.lang.AssertionError: This test requires a SIM card with carrier privilege rule on it. | 特殊SIM卡 |
| android.carrierapi.cts.ApnDatabaseTest#testUpdateConflictCase | fail | java.lang.AssertionError: This test requires a SIM card with carrier privilege rule on it. | 特殊SIM卡 |
| android.carrierapi.cts.ApnDatabaseTest#testValidCase | fail | java.lang.AssertionError: This test requires a SIM card with carrier privilege rule on it. | 特殊SIM卡 |
| android.carrierapi.cts.CarrierApiTest#testCarrierConfigIsAccessible | fail | junit.framework.AssertionFailedError: This test requires a SIM card with carrier privilege rule on it. | 特殊SIM卡 |
| android.carrierapi.cts.CarrierApiTest#testGetIccAuthentication | fail | junit.framework.AssertionFailedError: This test requires a SIM card with carrier privilege rule on it. | 特殊SIM卡 |
| android.carrierapi.cts.CarrierApiTest#testHasCarrierPrivileges | fail | junit.framework.AssertionFailedError: This test requires a SIM card with carrier privilege rule on it. | 特殊SIM卡 |
| android.carrierapi.cts.CarrierApiTest#testPhoneStateListener | fail | junit.framework.AssertionFailedError: This test requires a SIM card with carrier privilege rule on it. | 特殊SIM卡 |
| android.carrierapi.cts.CarrierApiTest#testSendDialerSpecialCode | fail | junit.framework.AssertionFailedError: This test requires a SIM card with carrier privilege rule on it. | 特殊SIM卡 |
| android.carrierapi.cts.CarrierApiTest#testSubscriptionInfoListing | fail | junit.framework.AssertionFailedError: getActiveSubscriptionInfoCount() should be non-zero | 特殊SIM卡 |
| android.carrierapi.cts.CarrierApiTest#testTelephonyApisAreAccessible | fail | junit.framework.AssertionFailedError: This test requires a SIM card with carrier privilege rule on it. | 特殊SIM卡 |
| android.carrierapi.cts.CarrierApiTest#testVoicemailStatusTableIsAccessible | fail | junit.framework.AssertionFailedError: This test requires a SIM card with carrier privilege rule on it. | 特殊SIM卡 |
| android.carrierapi.cts.CarrierApiTest#testVoicemailTableIsAccessible | fail | junit.framework.AssertionFailedError: This test requires a SIM card with carrier privilege rule on it. | 特殊SIM卡 |
| android.carrierapi.cts.NetworkScanApiTest#testRequestNetworkScan | fail | java.lang.AssertionError: This test requires a SIM card with carrier privilege rule on it. | 特殊SIM卡 |
| arm64-v8a CtsDevicePolicyManagerTestCases | |||
| Test | Result | Details | |
| com.android.cts.devicepolicy.ManagedProfileTest#testWipeDataWithReason | fail | java.lang.AssertionError: On-device tests failed: | |
| com.android.cts.devicepolicy.MixedDeviceOwnerTest#testKeyManagement | fail | java.lang.AssertionError: On-device tests failed: | key 相关 |
| com.android.cts.devicepolicy.MixedManagedProfileOwnerTest#testKeyManagement | fail | java.lang.AssertionError: On-device tests failed: | key 相关 |
| com.android.cts.devicepolicy.MixedProfileOwnerTest#testKeyManagement | fail | java.lang.AssertionError: On-device tests failed: | key 相关 |
| arm64-v8a CtsGraphicsTestCases | |||
| Test | Result | Details | |
| android.graphics.cts.VulkanFeaturesTest#testVulkanHardwareFeatures | fail | java.lang.AssertionError: System feature android.hardware.vulkan.level version 1 doesn't match best physical device hardware level 0 expected:<0> but was:<1> | 复测fail，习惯qcom/common/base.mk 在 VULKAN_FEATURE_LEVEL_0_TARGETS_LIST : 加上自己的项目 |
| arm64-v8a CtsInputMethodServiceHostTestCases | |||
| Test | Result | Details | |
| android.inputmethodservice.cts.hostside.InputMethodServiceLifecycleTest#testInputUnbindsOnImeStoppedFull | fail | java.lang.AssertionError: on-device tests failed: | 复测pass |
| arm64-v8a CtsKeystoreTestCases | |||
| Test | Result | Details | |
| android.keystore.cts.KeyAttestationTest#testEcAttestation | fail | java.lang.Exception: Failed on curve 0 and challege 0 | key 相关 |
| android.keystore.cts.KeyAttestationTest#testRsaAttestation | fail | java.lang.Exception: Failed on key size 512 challenge [], purposes [2, 3] and paddings [PKCS1] | key 相关 |
| arm64-v8a CtsLibcoreTestCases | |||
| Test | Result | Details | |
| libcore.java.net.InetAddressTest#test_getByName_invalid[1] | fail | java.lang.AssertionError: Invalid IP address incorrectly recognized as valid: 1.2.3.4. | IPV 6 |
| libcore.java.net.InetAddressTest#test_isReachable_by_ICMP | fail | java.lang.AssertionError | IPV 6 |
| arm64-v8a CtsNetTestCases | |||
| Test | Result | Details | |
| android.net.cts.ConnectivityManagerTest#testOpenConnection | fail | java.net.ConnectException: Failed to connect to google-ipv6test.appspot.com/31.13.72.34:80 | IPV 6 |
| android.net.cts.MultinetworkApiTest#testNativeDatagramTransmission | fail | android.system.ErrnoException: DatagramCheck on [type: WIFI[], state: CONNECTED/CONNECTED, reason: (unspecified), extra: (none), failover: false, available: true, roaming: false] failed: EPROTO (Protocol error) | IPV 6 或者特殊SIM卡 |
| arm64-v8a CtsOmapiTestCases | |||
| Test | Result | Details | |
| android.omapi.cts.OmapiTest#testATR | fail | java.lang.AssertionError: Could not open session | 特殊SIM卡 |
| android.omapi.cts.OmapiTest#testGetReaders | fail | java.lang.AssertionError | 特殊SIM卡 |
| android.omapi.cts.OmapiTest#testLongSelectResponse | fail | java.lang.AssertionError: Unexpected Exception java.lang.SecurityException: Exception in setUpChannelAccess()java.security.AccessControlException: SecureElement-AccessControlEnforceraccess denied: No ARF exists | 特殊SIM卡 |
| android.omapi.cts.OmapiTest#testOpenBasicChannelNonNullAid | fail | java.lang.AssertionError: Unexpected Exception java.io.IOException: Secure Element is not present. | 特殊SIM卡 |
| android.omapi.cts.OmapiTest#testOpenBasicChannelNullAid | fail | java.lang.AssertionError: Unexpected Exception java.io.IOException: Secure Element is not present. | 特殊SIM卡 |
| android.omapi.cts.OmapiTest#testP2Value | fail | java.lang.AssertionError: unexpected exception java.lang.SecurityException: Exception in setUpChannelAccess()java.security.AccessControlException: SecureElement-AccessControlEnforceraccess denied: No ARF exists | 特殊SIM卡 |
| android.omapi.cts.OmapiTest#testSecurityExceptionInTransmit | fail | java.lang.AssertionError: unexpected exception java.lang.SecurityException: Exception in setUpChannelAccess()java.security.AccessControlException: SecureElement-AccessControlEnforceraccess denied: No ARF exists | 特殊SIM卡 |
| android.omapi.cts.OmapiTest#testSegmentedResponseTransmit | fail | java.lang.AssertionError: unexpected exception java.lang.SecurityException: Exception in setUpChannelAccess()java.security.AccessControlException: SecureElement-AccessControlEnforceraccess denied: No ARF exists | 特殊SIM卡 |
| android.omapi.cts.OmapiTest#testSelectableAid | fail | java.lang.AssertionError: Unexpected Exception java.lang.SecurityException: Exception in setUpChannelAccess()java.security.AccessControlException: SecureElement-AccessControlEnforceraccess denied: No ARF exists | 特殊SIM卡 |
| android.omapi.cts.OmapiTest#testStatusWordTransmit | fail | java.lang.AssertionError: unexpected exception java.lang.SecurityException: Exception in setUpChannelAccess()java.security.AccessControlException: SecureElement-AccessControlEnforceraccess denied: No ARF exists | 特殊SIM卡 |
| android.omapi.cts.OmapiTest#testTransmitApdu | fail | java.lang.AssertionError: unexpected exception java.lang.SecurityException: Exception in setUpChannelAccess()java.security.AccessControlException: SecureElement-AccessControlEnforceraccess denied: No ARF exists | 特殊SIM卡 |
| android.omapi.cts.OmapiTest#testWrongAid | fail | java.lang.AssertionError: unexpected exception java.lang.SecurityException: Exception in setUpChannelAccess()java.security.AccessControlException: SecureElement-AccessControlEnforceraccess denied: No ARF exists | 特殊SIM卡 |
| arm64-v8a CtsPermission2TestCases | |||
| Test | Result | Details | |
| android.permission2.cts.NoReceiveSmsPermissionTest#testAppSpecificSmsToken | fail | junit.framework.AssertionFailedError: [RERUN] SIM card does not provide phone number. Use a suitable SIM Card. | 特殊SIM卡 |
| android.permission2.cts.NoReceiveSmsPermissionTest#testReceiveTextMessage | fail | junit.framework.AssertionFailedError: [RERUN] SIM card does not provide phone number. Use a suitable SIM Card. | 特殊SIM卡 |
| arm64-v8a CtsPreference2TestCases | |||
| Test | Result | Details | |
| android.preference2.cts.PreferenceActivityFlowLandscapeTest#backPressToExitLandscapeTest | fail | java.lang.AssertionError | 复测pass |
| android.preference2.cts.PreferenceActivityFlowLandscapeTest#goToFragmentLandscapeTest | fail | java.lang.AssertionError | 复测pass |
| android.preference2.cts.PreferenceActivityFlowLandscapeTest#listDialogLandscapeTest | fail | java.lang.AssertionError | 复测pass |
| android.preference2.cts.PreferenceActivityFlowLandscapeTest#recreateInnerFragmentLandscapeTest | fail | java.lang.AssertionError | 复测pass |
| android.preference2.cts.PreferenceActivityFlowLandscapeTest#smallScreenNoHighlightInHeadersListTest | fail | java.lang.AssertionError | 复测pass |
| android.preference2.cts.PreferenceActivityFlowLandscapeTest#startWithFragmentAndInitTitleLandscapeTest | fail | java.lang.AssertionError | 复测pass |
| android.preference2.cts.PreferenceActivityFlowLandscapeTest#startWithFragmentAndRecreateLandscapeTest | fail | java.lang.AssertionError | 复测pass |
| android.preference2.cts.PreferenceActivityFlowLandscapeTest#startWithFragmentLandscapeTest | fail | java.lang.AssertionError | 复测pass |
| android.preference2.cts.PreferenceActivityFlowLandscapeTest#startWithFragmentNoHeadersButInitTitleLandscapeTest | fail | java.lang.AssertionError | 复测pass |
| android.preference2.cts.PreferenceActivityFlowLandscapeTest#startWithFragmentNoHeadersLandscapeTest | fail | java.lang.AssertionError | 复测pass |
| android.preference2.cts.PreferenceActivityFlowLandscapeTest#switchHeadersLandscapeTest | fail | java.lang.AssertionError | 复测pass |
| android.preference2.cts.PreferenceActivityFlowPortraitTest#goToFragmentPortraitTest | fail | java.lang.AssertionError: View with text 'Fragment preference' was not found! | 复测pass |
| android.preference2.cts.PreferenceActivityFlowPortraitTest#listDialogPortraitTest | fail | java.lang.AssertionError: View with text 'List preference' was not found! | 复测pass |
| android.preference2.cts.PreferenceActivityFlowPortraitTest#recreateInnerFragmentPortraitTest | fail | java.lang.AssertionError | 复测pass |
| android.preference2.cts.PreferenceActivityFlowPortraitTest#smallScreenNoHighlightInHeadersListTest | fail | java.lang.AssertionError | 复测pass |
| android.preference2.cts.PreferenceActivityFlowPortraitTest#startWithFragmentAndRecreatePortraitTest | fail | java.lang.AssertionError: Screenshots do not match! | 复测pass |
| android.preference2.cts.PreferenceActivityFlowPortraitTest#startWithFragmentNoHeadersButInitTitlePortraitTest | fail | java.lang.AssertionError | 复测pass |
| android.preference2.cts.PreferenceActivityFlowPortraitTest#startWithFragmentPortraitTest | fail | java.lang.AssertionError | 复测pass |
| android.preference2.cts.PreferenceActivityFlowPortraitTest#switchHeadersPortraitTest | fail | java.lang.AssertionError | 复测pass |
| android.preference2.cts.PreferenceActivityLegacyFlowTest#legacyActivityTest | fail | java.lang.AssertionError | 复测pass |
| arm64-v8a CtsPrintTestCases | |||
| Test | Result | Details | |
| android.print.cts.CustomPrintOptionsTest#changeToAllPages | fail | java.lang.RuntimeException: android.support.test.uiautomator.UiObjectNotFoundException: Could not find printer Test printer even though we retried. | 复测pass |
| android.print.cts.CustomPrintOptionsTest#changeToAttributes | fail | Test failed to run to completion. Reason: 'Failed to receive adb shell test output within 1800000 ms. Test may have timed out, or adb connection to device became unresponsive'. Check device logcat for details | 复测pass |
| android.print.cts.CustomPrintOptionsTest#changeToAttributesNoCopy | fail | java.lang.RuntimeException: android.support.test.uiautomator.UiObjectNotFoundException: Could not find printer Test printer even though we retried. | 复测pass |
| android.print.cts.CustomPrintOptionsTest#changeToChangeEveryThingButPages | fail | java.lang.RuntimeException: android.support.test.uiautomator.UiObjectNotFoundException: Could not find printer Test printer even though we retried. | 复测pass |
| android.print.cts.CustomPrintOptionsTest#changeToDefault | fail | java.lang.RuntimeException: android.support.test.uiautomator.UiObjectNotFoundException: Could not find printer Test printer even though we retried. | 复测pass |
| android.print.cts.CustomPrintOptionsTest#changeToDefaultNoCopy | fail | java.lang.RuntimeException: android.support.test.uiautomator.UiObjectNotFoundException: Could not find printer Test printer even though we retried. | 复测pass |
| android.print.cts.CustomPrintOptionsTest#changeToNonAttributes | fail | Test failed to run to completion. Reason: 'Failed to receive adb shell test output within 1800000 ms. Test may have timed out, or adb connection to device became unresponsive'. Check device logcat for details | 复测pass |
| android.print.cts.CustomPrintOptionsTest#changeToNonAttributesNoCopy | fail | java.lang.RuntimeException: android.support.test.uiautomator.UiObjectNotFoundException: Could not find printer Test printer even though we retried. | 复测pass |
| android.print.cts.CustomPrintOptionsTest#changeToNothing | fail | java.lang.RuntimeException: android.support.test.uiautomator.UiObjectNotFoundException: Could not find printer Test printer even though we retried. | 复测pass |
| android.print.cts.CustomPrintOptionsTest#changeToSomePages | fail | java.lang.RuntimeException: android.support.test.uiautomator.UiObjectNotFoundException: Could not find printer Test printer even though we retried. | 复测pass |
| android.print.cts.CustomPrintOptionsTest#testChangeToNothingNoCopy | fail | java.lang.RuntimeException: android.support.test.uiautomator.UiObjectNotFoundException: Could not find printer Test printer even though we retried. | 复测pass |
| android.print.cts.PageRangeAdjustAndVerify#adjustPageRangeAndVerifyPages[0] | fail | android.support.test.uiautomator.UiObjectNotFoundException: Could not find printer First printer even though we retried. | 复测pass |
| android.print.cts.PageRangeAdjustAndVerify#adjustPageRangeAndVerifyPages[1] | fail | android.support.test.uiautomator.UiObjectNotFoundException: Could not find printer First printer even though we retried. | 复测pass |
| android.print.cts.PageRangeAdjustAndVerify#adjustPageRangeAndVerifyPages[2] | fail | android.support.test.uiautomator.UiObjectNotFoundException: Could not find printer First printer even though we retried. | 复测pass |
| android.print.cts.PageRangeAdjustmentTest#allPagesWantedAndAllPagesWritten | fail | java.lang.RuntimeException: Could not launch intent Intent { act=android.intent.action.MAIN flg=0x10000000 cmp=android.print.cts/android.print.test.PrintDocumentActivity (has extras) } within 45 seconds. Perhaps the main thread has not gone idle within a reasonable amount of time? There could be an animation or something constantly repainting the screen. Or the activity is doing network calls on creation? See the threaddump logs. For your reference the last time the event queue was idle before your activity launch request was 1575899209582 and now the last time the queue went idle was: 1575899246475. If these numbers are the same your activity might be hogging the event queue. | 复测pass |
| android.print.cts.PageRangeAdjustmentTest#somePagesWantedAndAllPagesWritten | fail | java.lang.AssertionError: Activity was not destroyed | 复测pass |
| android.print.cts.PageRangeAdjustmentTest#somePagesWantedAndNotWritten | fail | java.lang.RuntimeException: Could not launch intent Intent { act=android.intent.action.MAIN flg=0x10000000 cmp=android.print.cts/android.print.test.PrintDocumentActivity (has extras) } within 45 seconds. Perhaps the main thread has not gone idle within a reasonable amount of time? There could be an animation or something constantly repainting the screen. Or the activity is doing network calls on creation? See the threaddump logs. For your reference the last time the event queue was idle before your activity launch request was 1575899259287 and now the last time the queue went idle was: 1575899304444. If these numbers are the same your activity might be hogging the event queue. | 复测pass |
| android.print.cts.PageRangeAdjustmentTest#somePagesWantedAndSomeMorePagesWritten | fail | java.lang.RuntimeException: Could not launch intent Intent { act=android.intent.action.MAIN flg=0x10000000 cmp=android.print.cts/android.print.test.PrintDocumentActivity (has extras) } within 45 seconds. Perhaps the main thread has not gone idle within a reasonable amount of time? There could be an animation or something constantly repainting the screen. Or the activity is doing network calls on creation? See the threaddump logs. For your reference the last time the event queue was idle before your activity launch request was 1575899160109 and now the last time the queue went idle was: 1575899204291. If these numbers are the same your activity might be hogging the event queue. | 复测pass |
| android.print.cts.PageRangeAdjustmentTest#wantedPagesAlreadyWrittenForPreview | fail | java.lang.RuntimeException: Could not launch intent Intent { act=android.intent.action.MAIN flg=0x10000000 cmp=android.print.cts/android.print.test.PrintDocumentActivity (has extras) } within 45 seconds. Perhaps the main thread has not gone idle within a reasonable amount of time? There could be an animation or something constantly repainting the screen. Or the activity is doing network calls on creation? See the threaddump logs. For your reference the last time the event queue was idle before your activity launch request was 1575899108030 and now the last time the queue went idle was: 1575899155213. If these numbers are the same your activity might be hogging the event queue. | 复测pass |
| android.print.cts.PrintAttributesTest#suggestedDifferentFromDefault | fail | android.support.test.uiautomator.UiObjectNotFoundException: Could not find printer Test printer even though we retried. | 复测pass |
| android.print.cts.PrintDocumentAdapterContractTest#nonCallingBackWrite | fail | java.lang.RuntimeException: Could not launch intent Intent { act=android.intent.action.MAIN flg=0x10000000 cmp=android.print.cts/android.print.test.PrintDocumentActivity (has extras) } within 45 seconds. Perhaps the main thread has not gone idle within a reasonable amount of time? There could be an animation or something constantly repainting the screen. Or the activity is doing network calls on creation? See the threaddump logs. For your reference the last time the event queue was idle before your activity launch request was 1575897441987 and now the last time the queue went idle was: 1575897483621. If these numbers are the same your activity might be hogging the event queue. | 复测pass |
| android.print.cts.PrintDocumentAdapterContractTest#notEnoughPages | fail | java.lang.RuntimeException: Could not launch intent Intent { act=android.intent.action.MAIN flg=0x10000000 cmp=android.print.cts/android.print.test.PrintDocumentActivity (has extras) } within 45 seconds. Perhaps the main thread has not gone idle within a reasonable amount of time? There could be an animation or something constantly repainting the screen. Or the activity is doing network calls on creation? See the threaddump logs. For your reference the last time the event queue was idle before your activity launch request was 1575897243247 and now the last time the queue went idle was: 1575897288314. If these numbers are the same your activity might be hogging the event queue. | 复测pass |
| android.print.cts.PrintDocumentAdapterContractTest#nothingChangesAllPagesWrittenFirstTime | fail | java.lang.RuntimeException: Could not launch intent Intent { act=android.intent.action.MAIN flg=0x10000000 cmp=android.print.cts/android.print.test.PrintDocumentActivity (has extras) } within 45 seconds. Perhaps the main thread has not gone idle within a reasonable amount of time? There could be an animation or something constantly repainting the screen. Or the activity is doing network calls on creation? See the threaddump logs. For your reference the last time the event queue was idle before your activity launch request was 1575897342531 and now the last time the queue went idle was: 1575897386474. If these numbers are the same your activity might be hogging the event queue. | 复测pass |
| android.print.cts.PrintDocumentAdapterContractTest#printOptionsChangeAndPrinterChange | fail | java.lang.RuntimeException: Could not launch intent Intent { act=android.intent.action.MAIN flg=0x10000000 cmp=android.print.cts/android.print.test.PrintDocumentActivity (has extras) } within 45 seconds. Perhaps the main thread has not gone idle within a reasonable amount of time? There could be an animation or something constantly repainting the screen. Or the activity is doing network calls on creation? See the threaddump logs. For your reference the last time the event queue was idle before your activity launch request was 1575897392246 and now the last time the queue went idle was: 1575897437553. If these numbers are the same your activity might be hogging the event queue. | 复测pass |
| android.print.cts.PrintDocumentAdapterContractTest#unexpectedLayoutCancel | fail | java.lang.RuntimeException: Could not launch intent Intent { act=android.intent.action.MAIN flg=0x10000000 cmp=android.print.cts/android.print.test.PrintDocumentActivity (has extras) } within 45 seconds. Perhaps the main thread has not gone idle within a reasonable amount of time? There could be an animation or something constantly repainting the screen. Or the activity is doing network calls on creation? See the threaddump logs. For your reference the last time the event queue was idle before your activity launch request was 1575897292869 and now the last time the queue went idle was: 1575897337397. If these numbers are the same your activity might be hogging the event queue. | 复测pass |
| android.print.cts.PrintDocumentAdapterContractTest#unexpectedWriteCancel | fail | java.lang.AssertionError: Activity was not destroyed | 复测pass |
| android.print.cts.PrintJobStateTransitionsTest#stateTransitions[0] | fail | android.support.test.uiautomator.UiObjectNotFoundException: Could not find printer TestPrinter even though we retried. | 复测pass |
| android.print.cts.PrintJobStateTransitionsTest#stateTransitions[1] | fail | android.support.test.uiautomator.UiObjectNotFoundException: Could not find printer TestPrinter even though we retried. | 复测pass |
| android.print.cts.PrintJobStateTransitionsTest#stateTransitions[2] | fail | android.support.test.uiautomator.UiObjectNotFoundException: Could not find printer TestPrinter even though we retried. | 复测pass |
| android.print.cts.PrintJobStateTransitionsTest#stateTransitions[3] | fail | Test failed to run to completion. Reason: 'Failed to receive adb shell test output within 1800000 ms. Test may have timed out, or adb connection to device became unresponsive'. Check device logcat for details | 复测pass |
| android.print.cts.PrintJobStateTransitionsTest#stateTransitions[4] | fail | Test failed to run to completion. Reason: 'Failed to receive adb shell test output within 1800000 ms. Test may have timed out, or adb connection to device became unresponsive'. Check device logcat for details | 复测pass |
| android.print.cts.PrintJobStateTransitionsTest#stateTransitions[5] | fail | android.support.test.uiautomator.UiObjectNotFoundException: Could not find printer TestPrinter even though we retried. | 复测pass |
| android.print.cts.PrintJobTest#other | fail | Test failed to run to completion. Reason: 'Failed to receive adb shell test output within 1800000 ms. Test may have timed out, or adb connection to device became unresponsive'. Check device logcat for details | 复测pass |
| android.print.cts.PrintJobTest#tag | fail | android.support.test.uiautomator.UiObjectNotFoundException: Could not find printer TestPrinter even though we retried. | 复测pass |
| android.print.cts.PrintServicesTest#getActivePrintJobs | fail | android.support.test.uiautomator.UiObjectNotFoundException: Could not find printer Printer1 even though we retried. | 复测pass |
| android.print.cts.PrinterCapabilitiesChangeTest#changeCapabilities[0] | fail | java.lang.AssertionError: Activity was not destroyed | 复测pass |
| android.print.cts.PrinterCapabilitiesChangeTest#changeCapabilities[10] | fail | java.lang.RuntimeException: Could not launch intent Intent { act=android.intent.action.MAIN flg=0x10000000 cmp=android.print.cts/android.print.test.PrintDocumentActivity (has extras) } within 45 seconds. Perhaps the main thread has not gone idle within a reasonable amount of time? There could be an animation or something constantly repainting the screen. Or the activity is doing network calls on creation? See the threaddump logs. For your reference the last time the event queue was idle before your activity launch request was 1575898304820 and now the last time the queue went idle was: 1575898345955. If these numbers are the same your activity might be hogging the event queue. | 复测pass |
| android.print.cts.PrinterCapabilitiesChangeTest#changeCapabilities[11] | fail | java.lang.RuntimeException: Could not launch intent Intent { act=android.intent.action.MAIN flg=0x10000000 cmp=android.print.cts/android.print.test.PrintDocumentActivity (has extras) } within 45 seconds. Perhaps the main thread has not gone idle within a reasonable amount of time? There could be an animation or something constantly repainting the screen. Or the activity is doing network calls on creation? See the threaddump logs. For your reference the last time the event queue was idle before your activity launch request was 1575898354488 and now the last time the queue went idle was: 1575898399040. If these numbers are the same your activity might be hogging the event queue. | 复测pass |
| android.print.cts.PrinterCapabilitiesChangeTest#changeCapabilities[12] | fail | java.lang.RuntimeException: Could not launch intent Intent { act=android.intent.action.MAIN flg=0x10000000 cmp=android.print.cts/android.print.test.PrintDocumentActivity (has extras) } within 45 seconds. Perhaps the main thread has not gone idle within a reasonable amount of time? There could be an animation or something constantly repainting the screen. Or the activity is doing network calls on creation? See the threaddump logs. For your reference the last time the event queue was idle before your activity launch request was 1575898404157 and now the last time the queue went idle was: 1575898448115. If these numbers are the same your activity might be hogging the event queue. | 复测pass |
| android.print.cts.PrinterCapabilitiesChangeTest#changeCapabilities[13] | fail | java.lang.RuntimeException: Could not launch intent Intent { act=android.intent.action.MAIN flg=0x10000000 cmp=android.print.cts/android.print.test.PrintDocumentActivity (has extras) } within 45 seconds. Perhaps the main thread has not gone idle within a reasonable amount of time? There could be an animation or something constantly repainting the screen. Or the activity is doing network calls on creation? See the threaddump logs. For your reference the last time the event queue was idle before your activity launch request was 1575898453874 and now the last time the queue went idle was: 1575898499195. If these numbers are the same your activity might be hogging the event queue. | 复测pass |
| android.print.cts.PrinterCapabilitiesChangeTest#changeCapabilities[14] | fail | java.lang.RuntimeException: Could not launch intent Intent { act=android.intent.action.MAIN flg=0x10000000 cmp=android.print.cts/android.print.test.PrintDocumentActivity (has extras) } within 45 seconds. Perhaps the main thread has not gone idle within a reasonable amount of time? There could be an animation or something constantly repainting the screen. Or the activity is doing network calls on creation? See the threaddump logs. For your reference the last time the event queue was idle before your activity launch request was 1575898503618 and now the last time the queue went idle was: 1575898548925. If these numbers are the same your activity might be hogging the event queue. | 复测pass |
| android.print.cts.PrinterCapabilitiesChangeTest#changeCapabilities[15] | fail | java.lang.RuntimeException: Could not launch intent Intent { act=android.intent.action.MAIN flg=0x10000000 cmp=android.print.cts/android.print.test.PrintDocumentActivity (has extras) } within 45 seconds. Perhaps the main thread has not gone idle within a reasonable amount of time? There could be an animation or something constantly repainting the screen. Or the activity is doing network calls on creation? See the threaddump logs. For your reference the last time the event queue was idle before your activity launch request was 1575898553278 and now the last time the queue went idle was: 1575898598346. If these numbers are the same your activity might be hogging the event queue. | 复测pass |
| android.print.cts.PrinterCapabilitiesChangeTest#changeCapabilities[16] | fail | java.lang.RuntimeException: Could not launch intent Intent { act=android.intent.action.MAIN flg=0x10000000 cmp=android.print.cts/android.print.test.PrintDocumentActivity (has extras) } within 45 seconds. Perhaps the main thread has not gone idle within a reasonable amount of time? There could be an animation or something constantly repainting the screen. Or the activity is doing network calls on creation? See the threaddump logs. For your reference the last time the event queue was idle before your activity launch request was 1575898603060 and now the last time the queue went idle was: 1575898646419. If these numbers are the same your activity might be hogging the event queue. | 复测pass |
| android.print.cts.PrinterCapabilitiesChangeTest#changeCapabilities[17] | fail | java.lang.RuntimeException: Could not launch intent Intent { act=android.intent.action.MAIN flg=0x10000000 cmp=android.print.cts/android.print.test.PrintDocumentActivity (has extras) } within 45 seconds. Perhaps the main thread has not gone idle within a reasonable amount of time? There could be an animation or something constantly repainting the screen. Or the activity is doing network calls on creation? See the threaddump logs. For your reference the last time the event queue was idle before your activity launch request was 1575898652777 and now the last time the queue went idle was: 1575898696496. If these numbers are the same your activity might be hogging the event queue. | 复测pass |
| android.print.cts.PrinterCapabilitiesChangeTest#changeCapabilities[18] | fail | java.lang.RuntimeException: Could not launch intent Intent { act=android.intent.action.MAIN flg=0x10000000 cmp=android.print.cts/android.print.test.PrintDocumentActivity (has extras) } within 45 seconds. Perhaps the main thread has not gone idle within a reasonable amount of time? There could be an animation or something constantly repainting the screen. Or the activity is doing network calls on creation? See the threaddump logs. For your reference the last time the event queue was idle before your activity launch request was 1575898702504 and now the last time the queue went idle was: 1575898747574. If these numbers are the same your activity might be hogging the event queue. | 复测pass |
| android.print.cts.PrinterCapabilitiesChangeTest#changeCapabilities[19] | fail | java.lang.RuntimeException: Could not launch intent Intent { act=android.intent.action.MAIN flg=0x10000000 cmp=android.print.cts/android.print.test.PrintDocumentActivity (has extras) } within 45 seconds. Perhaps the main thread has not gone idle within a reasonable amount of time? There could be an animation or something constantly repainting the screen. Or the activity is doing network calls on creation? See the threaddump logs. For your reference the last time the event queue was idle before your activity launch request was 1575898752240 and now the last time the queue went idle was: 1575898797655. If these numbers are the same your activity might be hogging the event queue. | 复测pass |
| android.print.cts.PrinterCapabilitiesChangeTest#changeCapabilities[1] | fail | java.lang.RuntimeException: Could not launch intent Intent { act=android.intent.action.MAIN flg=0x10000000 cmp=android.print.cts/android.print.test.PrintDocumentActivity (has extras) } within 45 seconds. Perhaps the main thread has not gone idle within a reasonable amount of time? There could be an animation or something constantly repainting the screen. Or the activity is doing network calls on creation? See the threaddump logs. For your reference the last time the event queue was idle before your activity launch request was 1575897699959 and now the last time the queue went idle was: 1575897741663. If these numbers are the same your activity might be hogging the event queue. | 复测pass |
| android.print.cts.PrinterCapabilitiesChangeTest#changeCapabilities[20] | fail | java.lang.RuntimeException: Could not launch intent Intent { act=android.intent.action.MAIN flg=0x10000000 cmp=android.print.cts/android.print.test.PrintDocumentActivity (has extras) } within 45 seconds. Perhaps the main thread has not gone idle within a reasonable amount of time? There could be an animation or something constantly repainting the screen. Or the activity is doing network calls on creation? See the threaddump logs. For your reference the last time the event queue was idle before your activity launch request was 1575898802670 and now the last time the queue went idle was: 1575898846738. If these numbers are the same your activity might be hogging the event queue. | 复测pass |
| android.print.cts.PrinterCapabilitiesChangeTest#changeCapabilities[21] | fail | java.lang.RuntimeException: Could not launch intent Intent { act=android.intent.action.MAIN flg=0x10000000 cmp=android.print.cts/android.print.test.PrintDocumentActivity (has extras) } within 45 seconds. Perhaps the main thread has not gone idle within a reasonable amount of time? There could be an animation or something constantly repainting the screen. Or the activity is doing network calls on creation? See the threaddump logs. For your reference the last time the event queue was idle before your activity launch request was 1575898852749 and now the last time the queue went idle was: 1575898895438. If these numbers are the same your activity might be hogging the event queue. | 复测pass |
| android.print.cts.PrinterCapabilitiesChangeTest#changeCapabilities[2] | fail | java.lang.RuntimeException: Could not launch intent Intent { act=android.intent.action.MAIN flg=0x10000000 cmp=android.print.cts/android.print.test.PrintDocumentActivity (has extras) } within 45 seconds. Perhaps the main thread has not gone idle within a reasonable amount of time? There could be an animation or something constantly repainting the screen. Or the activity is doing network calls on creation? See the threaddump logs. For your reference the last time the event queue was idle before your activity launch request was 1575897749385 and now the last time the queue went idle was: 1575897793102. If these numbers are the same your activity might be hogging the event queue. | 复测pass |
| android.print.cts.PrinterCapabilitiesChangeTest#changeCapabilities[3] | fail | java.lang.RuntimeException: Could not launch intent Intent { act=android.intent.action.MAIN flg=0x10000000 cmp=android.print.cts/android.print.test.PrintDocumentActivity (has extras) } within 45 seconds. Perhaps the main thread has not gone idle within a reasonable amount of time? There could be an animation or something constantly repainting the screen. Or the activity is doing network calls on creation? See the threaddump logs. For your reference the last time the event queue was idle before your activity launch request was 1575897799055 and now the last time the queue went idle was: 1575897842100. If these numbers are the same your activity might be hogging the event queue. | 复测pass |
| android.print.cts.PrinterCapabilitiesChangeTest#changeCapabilities[4] | fail | java.lang.RuntimeException: Could not launch intent Intent { act=android.intent.action.MAIN flg=0x10000000 cmp=android.print.cts/android.print.test.PrintDocumentActivity (has extras) } within 45 seconds. Perhaps the main thread has not gone idle within a reasonable amount of time? There could be an animation or something constantly repainting the screen. Or the activity is doing network calls on creation? See the threaddump logs. For your reference the last time the event queue was idle before your activity launch request was 1575897849187 and now the last time the queue went idle was: 1575897893254. If these numbers are the same your activity might be hogging the event queue. | 复测pass |
| android.print.cts.PrinterCapabilitiesChangeTest#changeCapabilities[5] | fail | java.lang.AssertionError: Activity was not destroyed | 复测pass |
| android.print.cts.PrinterCapabilitiesChangeTest#changeCapabilities[6] | fail | java.lang.RuntimeException: Could not launch intent Intent { act=android.intent.action.MAIN flg=0x10000000 cmp=android.print.cts/android.print.test.PrintDocumentActivity (has extras) } within 45 seconds. Perhaps the main thread has not gone idle within a reasonable amount of time? There could be an animation or something constantly repainting the screen. Or the activity is doing network calls on creation? See the threaddump logs. For your reference the last time the event queue was idle before your activity launch request was 1575898103578 and now the last time the queue went idle was: 1575898149651. If these numbers are the same your activity might be hogging the event queue. | 复测pass |
| android.print.cts.PrinterCapabilitiesChangeTest#changeCapabilities[7] | fail | java.lang.RuntimeException: Could not launch intent Intent { act=android.intent.action.MAIN flg=0x10000000 cmp=android.print.cts/android.print.test.PrintDocumentActivity (has extras) } within 45 seconds. Perhaps the main thread has not gone idle within a reasonable amount of time? There could be an animation or something constantly repainting the screen. Or the activity is doing network calls on creation? See the threaddump logs. For your reference the last time the event queue was idle before your activity launch request was 1575898155062 and now the last time the queue went idle was: 1575898200729. If these numbers are the same your activity might be hogging the event queue. | 复测pass |
| android.print.cts.PrinterCapabilitiesChangeTest#changeCapabilities[8] | fail | java.lang.RuntimeException: Could not launch intent Intent { act=android.intent.action.MAIN flg=0x10000000 cmp=android.print.cts/android.print.test.PrintDocumentActivity (has extras) } within 45 seconds. Perhaps the main thread has not gone idle within a reasonable amount of time? There could be an animation or something constantly repainting the screen. Or the activity is doing network calls on creation? See the threaddump logs. For your reference the last time the event queue was idle before your activity launch request was 1575898205902 and now the last time the queue went idle was: 1575898250809. If these numbers are the same your activity might be hogging the event queue. | 复测pass |
| android.print.cts.PrinterCapabilitiesChangeTest#changeCapabilities[9] | fail | java.lang.RuntimeException: Could not launch intent Intent { act=android.intent.action.MAIN flg=0x10000000 cmp=android.print.cts/android.print.test.PrintDocumentActivity (has extras) } within 45 seconds. Perhaps the main thread has not gone idle within a reasonable amount of time? There could be an animation or something constantly repainting the screen. Or the activity is doing network calls on creation? See the threaddump logs. For your reference the last time the event queue was idle before your activity launch request was 1575898255096 and now the last time the queue went idle was: 1575898299884. If these numbers are the same your activity might be hogging the event queue. | 复测pass |
| android.print.cts.PrinterCapabilitiesTest#illegalPrinterCapabilityInfos | fail | java.lang.RuntimeException: Could not launch intent Intent { act=android.intent.action.MAIN flg=0x10000000 cmp=android.print.cts/android.print.test.PrintDocumentActivity (has extras) } within 45 seconds. Perhaps the main thread has not gone idle within a reasonable amount of time? There could be an animation or something constantly repainting the screen. Or the activity is doing network calls on creation? See the threaddump logs. For your reference the last time the event queue was idle before your activity launch request was 1575896935294 and now the last time the queue went idle was: 1575896979346. If these numbers are the same your activity might be hogging the event queue. | 复测pass |
| android.print.cts.PrinterCapabilitiesTest#invalidDefaultColor | fail | java.lang.RuntimeException: Could not launch intent Intent { act=android.intent.action.MAIN flg=0x10000000 cmp=android.print.cts/android.print.test.PrintDocumentActivity (has extras) } within 45 seconds. Perhaps the main thread has not gone idle within a reasonable amount of time? There could be an animation or something constantly repainting the screen. Or the activity is doing network calls on creation? See the threaddump logs. For your reference the last time the event queue was idle before your activity launch request was 1575896883681 and now the last time the queue went idle was: 1575896929209. If these numbers are the same your activity might be hogging the event queue. | 复测pass |
| android.print.cts.PrinterCapabilitiesTest#invalidDefaultDuplexMode | fail | java.lang.AssertionError: Activity was not destroyed | 复测pass |
| android.print.cts.PrinterCapabilitiesTest#sanePrinterCapabilityInfos | fail | java.lang.RuntimeException: Could not launch intent Intent { act=android.intent.action.MAIN flg=0x10000000 cmp=android.print.cts/android.print.test.PrintDocumentActivity (has extras) } within 45 seconds. Perhaps the main thread has not gone idle within a reasonable amount of time? There could be an animation or something constantly repainting the screen. Or the activity is doing network calls on creation? See the threaddump logs. For your reference the last time the event queue was idle before your activity launch request was 1575896984948 and now the last time the queue went idle was: 1575897030913. If these numbers are the same your activity might be hogging the event queue. | 复测pass |
| android.print.cts.PrinterDiscoverySessionLifecycleTest#defaultPrinterBecomesAvailableWhileInBackground | fail | java.lang.RuntimeException: Could not launch intent Intent { act=android.intent.action.MAIN flg=0x10000000 cmp=android.print.cts/android.print.test.PrintDocumentActivity (has extras) } within 45 seconds. Perhaps the main thread has not gone idle within a reasonable amount of time? There could be an animation or something constantly repainting the screen. Or the activity is doing network calls on creation? See the threaddump logs. For your reference the last time the event queue was idle before your activity launch request was 1575908769722 and now the last time the queue went idle was: 1575908810020. If these numbers are the same your activity might be hogging the event queue. | 复测pass |
| android.print.cts.PrinterDiscoverySessionLifecycleTest#defaultPrinterBecomesUsableWhileInBackground | fail | java.lang.RuntimeException: Could not launch intent Intent { act=android.intent.action.MAIN flg=0x10000000 cmp=android.print.cts/android.print.test.PrintDocumentActivity (has extras) } within 45 seconds. Perhaps the main thread has not gone idle within a reasonable amount of time? There could be an animation or something constantly repainting the screen. Or the activity is doing network calls on creation? See the threaddump logs. For your reference the last time the event queue was idle before your activity launch request was 1575908717892 and now the last time the queue went idle was: 1575908763949. If these numbers are the same your activity might be hogging the event queue. | 复测pass |
| android.print.cts.PrinterDiscoverySessionLifecycleTest#startPrinterDiscoveryWithHistoricalPrinters | fail | java.lang.AssertionError: Activity was not destroyed | 复测pass |
| arm64-v8a CtsProviderTestCases | |||
| Test | Result | Details | |
| android.provider.cts.MediaStoreUiTest#testImageCapture | fail | junit.framework.AssertionFailedError: Expected to get a IMAGE_CAPTURE result; your camera app should respond to the CAMERA and DPAD_CENTER keycodes | 复测pass |
| arm64-v8a CtsSecureElementAccessControlTestCases1 | |||
| Test | Result | Details | |
| android.omapi.accesscontrol1.cts.AccessControlTest#testAuthorizedAID | fail | java.lang.AssertionError: Unexpected Exception java.lang.SecurityException: Exception in setUpChannelAccess()java.security.AccessControlException: SecureElement-AccessControlEnforceraccess denied: No ARF exists | 特殊SIM 卡测试，如白卡 |
| android.omapi.accesscontrol1.cts.AccessControlTest#testAuthorizedAPDUAID40 | fail | java.lang.AssertionError: Unexpected Exception java.lang.SecurityException: Exception in setUpChannelAccess()java.security.AccessControlException: SecureElement-AccessControlEnforceraccess denied: No ARF exists | 特殊SIM 卡测试，如白卡 |
| android.omapi.accesscontrol1.cts.AccessControlTest#testAuthorizedAPDUAID41 | fail | java.lang.AssertionError: Unexpected Exception java.lang.SecurityException: Exception in setUpChannelAccess()java.security.AccessControlException: SecureElement-AccessControlEnforceraccess denied: No ARF exists | 特殊SIM 卡测试，如白卡 |
| android.omapi.accesscontrol1.cts.AccessControlTest#testUnauthorisedAPDUAID40 | fail | java.lang.AssertionError: Unexpected Exception java.lang.SecurityException: Exception in setUpChannelAccess()java.security.AccessControlException: SecureElement-AccessControlEnforceraccess denied: No ARF exists | 特殊SIM 卡测试，如白卡 |
| android.omapi.accesscontrol1.cts.AccessControlTest#testUnauthorisedAPDUAID41 | fail | java.lang.AssertionError: Unexpected Exception java.lang.SecurityException: Exception in setUpChannelAccess()java.security.AccessControlException: SecureElement-AccessControlEnforceraccess denied: No ARF exists | 特殊SIM 卡测试，如白卡 |
| android.omapi.accesscontrol1.cts.AccessControlTest#testUnauthorizedAID | fail | java.lang.AssertionError | 特殊SIM 卡测试，如白卡 |
| arm64-v8a CtsSecureElementAccessControlTestCases2 | |||
| Test | Result | Details | |
| android.omapi.accesscontrol2.cts.AccessControlTest#testAuthorizedAID | fail | java.lang.AssertionError: Unexpected Exception java.lang.SecurityException: Exception in setUpChannelAccess()java.security.AccessControlException: SecureElement-AccessControlEnforceraccess denied: No ARF exists | 特殊SIM 卡测试，如白卡 |
| android.omapi.accesscontrol2.cts.AccessControlTest#testAuthorizedAPDUAID40 | fail | java.lang.AssertionError: Unexpected Exception java.lang.SecurityException: Exception in setUpChannelAccess()java.security.AccessControlException: SecureElement-AccessControlEnforceraccess denied: No ARF exists | 特殊SIM 卡测试，如白卡 |
| android.omapi.accesscontrol2.cts.AccessControlTest#testAuthorizedAPDUAID41 | fail | java.lang.AssertionError: Unexpected Exception java.lang.SecurityException: Exception in setUpChannelAccess()java.security.AccessControlException: SecureElement-AccessControlEnforceraccess denied: No ARF exists | 特殊SIM 卡测试，如白卡 |
| android.omapi.accesscontrol2.cts.AccessControlTest#testUnauthorisedAPDUAID40 | fail | java.lang.AssertionError: Unexpected Exception java.lang.SecurityException: Exception in setUpChannelAccess()java.security.AccessControlException: SecureElement-AccessControlEnforceraccess denied: No ARF exists | 特殊SIM 卡测试，如白卡 |
| android.omapi.accesscontrol2.cts.AccessControlTest#testUnauthorisedAPDUAID41 | fail | java.lang.AssertionError: Unexpected Exception java.lang.SecurityException: Exception in setUpChannelAccess()java.security.AccessControlException: SecureElement-AccessControlEnforceraccess denied: No ARF exists | 特殊SIM 卡测试，如白卡 |
| android.omapi.accesscontrol2.cts.AccessControlTest#testUnauthorizedAID | fail | java.lang.AssertionError | 特殊SIM 卡测试，如白卡 |
| arm64-v8a CtsSecureElementAccessControlTestCases3 | |||
| Test | Result | Details | |
| android.omapi.accesscontrol3.cts.AccessControlTest#testAuthorizedAID | fail | java.lang.AssertionError: Unexpected Exception java.lang.SecurityException: Exception in setUpChannelAccess()java.security.AccessControlException: SecureElement-AccessControlEnforceraccess denied: No ARF exists | 特殊SIM 卡测试，如白卡 |
| android.omapi.accesscontrol3.cts.AccessControlTest#testAuthorizedAPDUAID40 | fail | java.lang.AssertionError: Unexpected Exception java.lang.SecurityException: Exception in setUpChannelAccess()java.security.AccessControlException: SecureElement-AccessControlEnforceraccess denied: No ARF exists | 特殊SIM 卡测试，如白卡 |
| android.omapi.accesscontrol3.cts.AccessControlTest#testAuthorizedAPDUAID41 | fail | java.lang.AssertionError: Unexpected Exception java.lang.SecurityException: Exception in setUpChannelAccess()java.security.AccessControlException: SecureElement-AccessControlEnforceraccess denied: No ARF exists | 特殊SIM 卡测试，如白卡 |
| android.omapi.accesscontrol3.cts.AccessControlTest#testUnauthorisedAPDUAID41 | fail | java.lang.AssertionError: Unexpected Exception java.lang.SecurityException: Exception in setUpChannelAccess()java.security.AccessControlException: SecureElement-AccessControlEnforceraccess denied: No ARF exists | 特殊SIM 卡测试，如白卡 |
| android.omapi.accesscontrol3.cts.AccessControlTest#testUnauthorizedAID | fail | java.lang.AssertionError | 特殊SIM 卡测试，如白卡 |
| arm64-v8a CtsSecurityTestCases | |||
| Test | Result | Details | |
| android.security.cts.PackageSignatureTest#testPackageSignatures | fail | junit.framework.AssertionFailedError: These packages should not be signed with a well known key: [com.android.storagemanager, com.android.printspooler, com.android.backup, com.android.defcontainer, com.android.systemui.overlay.ct, com.qualcomm.qti.poweroffalarm, com.android.protips, com.qualcomm.qti.simsettings, com.android.pacprocessor, android.telephony.overlay.cmcc, com.android.wallpaper.livepicker, com.android.providers.telephony, com.qualcomm.qti.ltedirect, com.qualcomm.qti.networksetting, com.qualcomm.qti.roamingsettings, com.android.providers.contacts, com.qualcomm.qti.qmmi, com.qualcomm.qti.qms.service.trustzoneaccess, com.android.mtp, com.android.sharedstoragebackup, com.android.documentsui, com.android.launcher3, com.android.bookmarkprovider, com.android.dialogs, org.codeaurora.gallery, com.google.android.gmsintegration, com.qualcomm.qti.autoregistration, com.android.emergency, com.android.internal.display.cutout.emulation.corner, com.qualcomm.simcontacts, com.android.carrierdefaultapp, com.qualcomm.qti.optinoverlay, com.qualcomm.qti.dynamicddsservice, com.android.location.fused, com.android.statementservice, com.android.systemui.overlay.cmcc, com.android.systemui.theme.dark, com.android.providers.settings, com.qti.qualcomm.datastatusnotification, com.android.systemui, org.codeaurora.ims, com.android.bips, com.android.companiondevicemanager, com.qualcomm.location, com.android.dreams.basic, com.qualcomm.qti.remoteSimlockAuth, com.qualcomm.qcrilmsgtunnel, com.android.shell, com.qualcomm.embms, com.qti.xdivert, com.android.backupconfirm, com.qualcomm.timeservice, com.android.settings, com.android.providers.userdictionary, com.qualcomm.qti.ims, com.qualcomm.qti.telephonyservice, com.android.soundrecorder, com.qualcomm.qti.confdialer, com.android.settings.intelligence, com.qti.dpmserviceapp, com.android.bluetoothmidiservice, com.android.internal.display.cutout.emulation.double, com.android.carrierconfig, com.android.phone, com.android.mms.service, com.android.egg, com.android.captiveportallogin, com.android.inputdevices, cn.nubia.systemupdate, com.android.calllogbackup, com.android.providers.partnerbookmarks, com.android.providers.calendar, com.qti.confuridialer, com.android.externalstorage, org.codeaurora.bluetooth, com.qualcomm.qti.callfeaturessetting, com.qualcomm.qti.services.secureui, com.android.server.telecom, android.ui.overlay.ct, com.android.keychain, com.android.wallpaperbackup, cn.nubia.factory, com.android.networksettings.overlay.ct, com.android.managedprovisioning, com.android.providers.media, com.android.stk, com.cyanogenmod.filemanager, com.android.wallpapercropper, com.android.mms.overlay.cmcc, android, org.codeaurora.snapcam, cn.nubia.advanced, com.android.certinstaller, com.android.settings.overlay.cmcc, com.qualcomm.qti.qtisystemservice, com.android.se, com.android.proxyhandler, com.android.simappdialog, com.android.musicfx, com.android.music, com.android.smspush, com.android.providers.downloads, com.qti.qualcomm.deviceinfo, com.qualcomm.atfwd, com.android.internal.display.cutout.emulation.tall, com.android.bluetooth, com.qualcomm.location.XT, com.android.providers.downloads.ui, com.qualcomm.qti.lpa, com.qti.diagservices, com.android.providers.blockednumber, com.qualcomm.qti.uim, com.android.traceur, com.qualcomm.qti.callenhancement, com.android.htmlviewer] | 复测pass, 已经修改使用自己制作的系统签名文件 |
| arm64-v8a CtsSyncAccountAccessOtherCertTestCases | |||
| Test | Result | Details | |
| com.android.cts.content.CtsSyncAccountAccessOtherCertTestCases#testAccountAccess_otherCertAsAuthenticatorCanNotSeeAccount | fail | java.lang.NullPointerException: Attempt to invoke virtual method 'void android.support.test.uiautomator.UiObject2.click()' on a null object reference | 机构可以测过 |
| arm64-v8a CtsTelephonyTestCases | |||
| Test | Result | Details | |
| android.telephony.cts.MmsTest#testSendMmsMessage | fail | junit.framework.AssertionFailedError | 特殊SIM 卡测试，如外网卡，白卡 |
| android.telephony.cts.SmsManagerTest#testSendAndReceiveMessages | fail | junit.framework.AssertionFailedError: [RERUN] SIM card does not provide phone number. Use a suitable SIM Card. | 特殊SIM 卡测试，如外网卡，白卡 |
| android.telephony.cts.SmsManagerTest#testSmsBlocking | fail | junit.framework.AssertionFailedError: [RERUN] SIM card does not provide phone number. Use a suitable SIM Card. | 特殊SIM 卡测试，如外网卡，白卡 |
| android.telephony.cts.SmsManagerTest#testSmsNotPersisted_failsWithoutCarrierPermissions | fail | junit.framework.AssertionFailedError: [RERUN] SIM card does not provide phone number. Use a suitable SIM Card. | 特殊SIM 卡测试，如外网卡，白卡 |
| android.telephony.cts.VisualVoicemailServiceTest#testFilter | fail | java.lang.IllegalArgumentException: Invalid destinationAddress | 特殊SIM 卡测试，如外网卡，白卡 |
| android.telephony.cts.VisualVoicemailServiceTest#testFilterFail_InvalidKeyValuePair | fail | java.lang.IllegalArgumentException: Invalid destinationAddress | 特殊SIM 卡测试，如外网卡，白卡 |
| android.telephony.cts.VisualVoicemailServiceTest#testFilterFail_InvalidMissingKey | fail | java.lang.IllegalArgumentException: Invalid destinationAddress | 特殊SIM 卡测试，如外网卡，白卡 |
| android.telephony.cts.VisualVoicemailServiceTest#testFilterFail_MessageEndAfterClientPrefix | fail | java.lang.IllegalArgumentException: Invalid destinationAddress | 特殊SIM 卡测试，如外网卡，白卡 |
| android.telephony.cts.VisualVoicemailServiceTest#testFilterFail_MessageEndAfterPrefix | fail | java.lang.IllegalArgumentException: Invalid destinationAddress | 特殊SIM 卡测试，如外网卡，白卡 |
| android.telephony.cts.VisualVoicemailServiceTest#testFilterFail_MissingFirstColon | fail | java.lang.IllegalArgumentException: Invalid destinationAddress | 特殊SIM 卡测试，如外网卡，白卡 |
| android.telephony.cts.VisualVoicemailServiceTest#testFilterFail_MissingSecondColon | fail | java.lang.IllegalArgumentException: Invalid destinationAddress | 特殊SIM 卡测试，如外网卡，白卡 |
| android.telephony.cts.VisualVoicemailServiceTest#testFilterFail_NotVvm | fail | java.lang.IllegalArgumentException: Invalid destinationAddress | 特殊SIM 卡测试，如外网卡，白卡 |
| android.telephony.cts.VisualVoicemailServiceTest#testFilterFail_PrefixMismatch | fail | java.lang.IllegalArgumentException: Invalid destinationAddress | 特殊SIM 卡测试，如外网卡，白卡 |
| android.telephony.cts.VisualVoicemailServiceTest#testFilter_EmptyField | fail | java.lang.IllegalArgumentException: Invalid destinationAddress | 特殊SIM 卡测试，如外网卡，白卡 |
| android.telephony.cts.VisualVoicemailServiceTest#testFilter_EmptyPrefix | fail | java.lang.IllegalArgumentException: Invalid destinationAddress | 特殊SIM 卡测试，如外网卡，白卡 |
| android.telephony.cts.VisualVoicemailServiceTest#testFilter_MissingValue | fail | java.lang.IllegalArgumentException: Invalid destinationAddress | 特殊SIM 卡测试，如外网卡，白卡 |
| android.telephony.cts.VisualVoicemailServiceTest#testFilter_TrailingSemiColon | fail | java.lang.IllegalArgumentException: Invalid destinationAddress | 特殊SIM 卡测试，如外网卡，白卡 |
| android.telephony.cts.VisualVoicemailServiceTest#testFilter_data | fail | java.lang.IllegalArgumentException: Invalid destinationAddress | 特殊SIM 卡测试，如外网卡，白卡 |
| android.telephony.cts.VisualVoicemailServiceTest#testFilter_originatingNumber_match_filtered | fail | java.lang.IllegalArgumentException: Invalid destinationAddress | 特殊SIM 卡测试，如外网卡，白卡 |
| android.telephony.cts.VisualVoicemailServiceTest#testFilter_originatingNumber_mismatch_notFiltered | fail | java.lang.IllegalArgumentException: Invalid destinationAddress | 特殊SIM 卡测试，如外网卡，白卡 |
| android.telephony.cts.VisualVoicemailServiceTest#testFilter_port_anydata | fail | java.lang.IllegalArgumentException: Invalid destinationAddress | 特殊SIM 卡测试，如外网卡，白卡 |
| android.telephony.cts.VisualVoicemailServiceTest#testFilter_port_anydata_notData | fail | java.lang.IllegalArgumentException: Invalid destinationAddress | 特殊SIM 卡测试，如外网卡，白卡 |
| android.telephony.cts.VisualVoicemailServiceTest#testFilter_port_match | fail | java.lang.IllegalArgumentException: Invalid destinationAddress | 特殊SIM 卡测试，如外网卡，白卡 |
| android.telephony.cts.VisualVoicemailServiceTest#testFilter_port_mismatch | fail | java.lang.IllegalArgumentException: Invalid destinationAddress | 特殊SIM 卡测试，如外网卡，白卡 |
| android.telephony.cts.VisualVoicemailServiceTest#testPermissionlessService_ignored | fail | java.lang.IllegalArgumentException: Invalid destinationAddress | 特殊SIM 卡测试，如外网卡，白卡 |
| android.telephony.gsm.cts.SmsManagerTest#testSendAndReceiveMessages | fail | junit.framework.AssertionFailedError: [RERUN] SIM card does not provide phone number. Use a suitable SIM Card. | 特殊SIM 卡测试，如外网卡，白卡 |
| android.telephony.gsm.cts.SmsManagerTest#testSmsBlocking | fail | junit.framework.AssertionFailedError: [RERUN] SIM card does not provide phone number. Use a suitable SIM Card. | 特殊SIM 卡测试，如外网卡，白卡 |
| android.telephony.gsm.cts.SmsManagerTest#testSmsNotPersisted_failsWithoutCarrierPermissions | fail | junit.framework.AssertionFailedError: [RERUN] SIM card does not provide phone number. Use a suitable SIM Card. | 特殊SIM 卡测试，如外网卡，白卡 |
| arm64-v8a CtsWebkitTestCases | |||
| Test | Result | Details | |
| android.webkit.cts.CookieManagerTest#testThirdPartyCookie | fail | junit.framework.AssertionFailedError: Action failed to complete before timeout | 复测fail |
| android.webkit.cts.WebViewClientTest#testShouldInterceptRequestResponse | fail | junit.framework.AssertionFailedError: unexpected timeout | 复测fail |
| android.webkit.cts.WebViewClientTest#testShouldOverrideUrlLoadingOnCreateWindow | fail | junit.framework.AssertionFailedError: unexpected timeout | 复测fail |
| android.webkit.cts.WebViewTest#testStartSafeBrowsingInvokesCallback | fail | junit.framework.AssertionFailedError: unexpected timeout | 复测fail |
| android.webkit.cts.WebViewTest#testStartSafeBrowsingUseApplicationContext | fail | junit.framework.AssertionFailedError: unexpected timeout | 复测fail |
| arm64-v8a CtsWidgetTestCases | |||
| Test | Result | Details | |
| android.widget.cts.AbsListViewTest#testMultiSelectionWithLongPressAndTaps | fail | junit.framework.AssertionFailedError: unexpected timeout | 复测pass |
| android.widget.cts.CheckBoxTest#testToggleViaEmulatedTap | fail | Wanted but not invoked: | 复测pass |
| android.widget.cts.NumberPickerTest#testInteractionWithSwipeDown | fail | java.lang.AssertionError: expected:<6> but was:<7> | 复测pass |
| android.widget.cts.RadioButtonTest#testToggleViaEmulatedTap | fail | Wanted but not invoked: | 复测pass |
| android.widget.cts.SpinnerTest#testDropDownBackgroundDropdownMode | fail | java.lang.AssertionError | 复测pass |
| android.widget.cts.SpinnerTest#testDropDownMetricsDropdownMode | fail | java.lang.AssertionError | 复测pass |
| android.widget.cts.TextViewTest#testAccessAutoLinkMask | fail | junit.framework.AssertionFailedError: unexpected timeout | 复测pass |
| android.widget.cts.TextViewTest#testAccessFreezesText | fail | junit.framework.AssertionFailedError: unexpected timeout | 复测pass |
| android.widget.cts.TextViewTest#testAccessText | fail | junit.framework.AssertionFailedError: unexpected timeout | 复测pass |
| android.widget.cts.TextViewTest#testAppend_addsLinksWhenTextIsSpannableAndContainsUrlAndAutoLinkIsEnabled | fail | junit.framework.AssertionFailedError: unexpected timeout | 复测pass |
| android.widget.cts.TextViewTest#testAutoSizeCallers_setCompoundDrawables | fail | junit.framework.AssertionFailedError: unexpected timeout | 复测pass |
| android.widget.cts.TextViewTest#testAutoSizeCallers_setMaxWidth | fail | junit.framework.AssertionFailedError: unexpected timeout | 复测pass |
| android.widget.cts.TextViewTest#testAutoSizeCallers_setTextSizeIsNoOp | fail | junit.framework.AssertionFailedError: unexpected timeout | 复测pass |
| android.widget.cts.TextViewTest#testAutoSizeCallers_setTransformationMethod | fail | junit.framework.AssertionFailedError: unexpected timeout | 复测pass |
| android.widget.cts.TextViewTest#testBeginEndBatchEditAreNotCalledForNonEditableText | fail | junit.framework.AssertionFailedError: unexpected timeout | 复测pass |
| android.widget.cts.TextViewTest#testClearComposingText | fail | junit.framework.AssertionFailedError: unexpected timeout | 复测pass |
| android.widget.cts.TextViewTest#testClickableSpanOnClickSingleTapOutside | fail | junit.framework.AssertionFailedError: unexpected timeout | 复测pass |
| android.widget.cts.TextViewTest#testDebug | fail | junit.framework.AssertionFailedError: unexpected timeout | 复测pass |
| android.widget.cts.TextViewTest#testEllipsizeAndMaxLinesForHint | fail | junit.framework.AssertionFailedError: unexpected timeout | 复测pass |
| android.widget.cts.TextViewTest#testGetBaseLine | fail | junit.framework.AssertionFailedError: unexpected timeout | 复测pass |
| android.widget.cts.TextViewTest#testGetDefaultEditable | fail | junit.framework.AssertionFailedError: unexpected timeout | 复测pass |
| android.widget.cts.TextViewTest#testGetOffsetForPositionSingleLineLtr | fail | junit.framework.AssertionFailedError: unexpected timeout | 复测pass |
| android.widget.cts.TextViewTest#testGetTotalPaddingRight | fail | junit.framework.AssertionFailedError: unexpected timeout | 复测pass |
| android.widget.cts.TextViewTest#testHeight | fail | junit.framework.AssertionFailedError: unexpected timeout | 复测pass |
| android.widget.cts.TextViewTest#testHyphenationNotHappen_breakStrategySimple | fail | junit.framework.AssertionFailedError: unexpected timeout | 复测pass |
| android.widget.cts.TextViewTest#testHyphenationNotHappen_frequencyNone | fail | junit.framework.AssertionFailedError: unexpected timeout | 复测pass |
| android.widget.cts.TextViewTest#testKeyNavigation | fail | junit.framework.AssertionFailedError: unexpected timeout | 复测pass |
| android.widget.cts.TextViewTest#testOnSaveInstanceState_doesNotRestoreSelectionWhenTextIsAbsent | fail | junit.framework.AssertionFailedError: unexpected timeout | 复测pass |
| android.widget.cts.TextViewTest#testSetElegantLineHeight | fail | junit.framework.AssertionFailedError: unexpected timeout | 复测pass |
| android.widget.cts.TextViewTest#testSetLetterSpacingChangesTextWidth | fail | junit.framework.AssertionFailedError: unexpected timeout | 复测pass |
| android.widget.cts.TextViewTest#testSetLineHeight | fail | junit.framework.AssertionFailedError: unexpected timeout | 复测pass |
| android.widget.cts.TextViewTest#testSetLineHeight_negative | fail | junit.framework.AssertionFailedError: unexpected timeout | 复测pass |
| android.widget.cts.TextViewTest#testSetPadding | fail | junit.framework.AssertionFailedError: unexpected timeout | 复测pass |
| android.widget.cts.TextViewTest#testSetShadowLayer | fail | junit.framework.AssertionFailedError: unexpected timeout | 复测pass |
| android.widget.cts.TextViewTest#testSetTextAppearance | fail | junit.framework.AssertionFailedError: unexpected timeout | 复测pass |
| android.widget.cts.TextViewTest#testTextIsSelectableFocusAndOnClick | fail | junit.framework.AssertionFailedError: unexpected timeout | 复测pass |
| android.widget.cts.TextViewTest#testUndo_textWatcherDirectAppend | fail | junit.framework.AssertionFailedError: unexpected timeout | 复测pass |
| android.widget.cts.ToolbarTest#testKeyShortcuts | fail | java.lang.SecurityException: Injecting to another application requires INJECT_EVENTS permission | 复测pass |
| arm64-v8a CtsWindowManagerDeviceTestCases | |||
| Test | Result | Details | |
| android.server.wm.CrossAppDragAndDropTests#testCancelSoon | fail | java.lang.AssertionError: Missing START_DRAG | 复测pass |
| android.server.wm.CrossAppDragAndDropTests#testDisallowGlobal | fail | java.lang.AssertionError: Missing START_DRAG | 复测pass |
| android.server.wm.CrossAppDragAndDropTests#testDisallowGlobalBelowSdk24 | fail | java.lang.AssertionError: Missing START_DRAG | 复测pass |
| android.server.wm.CrossAppDragAndDropTests#testFileUriGlobal | fail | java.lang.AssertionError: Missing START_DRAG | 复测pass |
| android.server.wm.CrossAppDragAndDropTests#testFileUriLocal | fail | java.lang.AssertionError: Missing START_DRAG | 复测pass |
| android.server.wm.CrossAppDragAndDropTests#testGrantNoneRequestNone | fail | java.lang.AssertionError: Missing START_DRAG | 复测pass |
| android.server.wm.CrossAppDragAndDropTests#testGrantNoneRequestRead | fail | java.lang.AssertionError: Missing START_DRAG | 复测pass |
| android.server.wm.CrossAppDragAndDropTests#testGrantNoneRequestWrite | fail | java.lang.AssertionError: Missing START_DRAG | 复测pass |
| android.server.wm.CrossAppDragAndDropTests#testGrantPersistableRequestTakePersistable | fail | java.lang.AssertionError: Missing START_DRAG | 复测pass |
| android.server.wm.CrossAppDragAndDropTests#testGrantReadNoPrefixRequestReadNested | fail | java.lang.AssertionError: Missing START_DRAG | 复测pass |
| android.server.wm.CrossAppDragAndDropTests#testGrantReadPrefixRequestReadNested | fail | java.lang.AssertionError: Missing START_DRAG | 复测pass |
| android.server.wm.CrossAppDragAndDropTests#testGrantReadRequestNone | fail | java.lang.AssertionError: Missing START_DRAG | 复测pass |
| android.server.wm.CrossAppDragAndDropTests#testGrantReadRequestRead | fail | java.lang.AssertionError: Missing START_DRAG | 复测pass |
| android.server.wm.CrossAppDragAndDropTests#testGrantReadRequestTakePersistable | fail | java.lang.AssertionError: Missing START_DRAG | 复测pass |
| android.server.wm.CrossAppDragAndDropTests#testGrantReadRequestWrite | fail | java.lang.AssertionError: Missing START_DRAG | 复测pass |
| android.server.wm.CrossAppDragAndDropTests#testGrantWriteRequestNone | fail | java.lang.AssertionError: Missing START_DRAG | 复测pass |
| android.server.wm.CrossAppDragAndDropTests#testGrantWriteRequestRead | fail | java.lang.AssertionError: Missing START_DRAG | 复测pass |
| android.server.wm.CrossAppDragAndDropTests#testGrantWriteRequestWrite | fail | java.lang.AssertionError: Missing START_DRAG | 复测pass |
| android.server.wm.DialogFrameTests#testDialogReceivesFocus | fail | org.junit.ComparisonFailure: expected:<[TestDialog]> but was:<[StatusBar]> | 复测pass |
| android.server.wm.DialogFrameTests#testNoFocusDialog | fail | org.junit.ComparisonFailure: expected:<[android.server.cts.wm/android.server.wm.DialogFrameTestActivity]> but was:<[StatusBar]> | 复测pass |
| android.server.wm.DisplayCutoutTests#testDisplayCutout_default_portrait | fail | junit.framework.AssertionFailedError: unexpected timeout | 复测pass |
| android.server.wm.DisplayCutoutTests#testDisplayCutout_never_portrait | fail | junit.framework.AssertionFailedError: unexpected timeout | 复测pass |
| android.server.wm.DisplayCutoutTests#testDisplayCutout_shortEdges_portrait | fail | junit.framework.AssertionFailedError: unexpected timeout | 复测pass |
| android.server.wm.LocationInWindowTests#testLocationInWindow_appWindow | fail | junit.framework.AssertionFailedError: unexpected timeout | 复测pass |
| android.server.wm.LocationInWindowTests#testLocationInWindow_appWindow_displayCutoutNever | fail | junit.framework.AssertionFailedError: unexpected timeout | 复测pass |
| android.server.wm.LocationInWindowTests#testLocationInWindow_appWindow_displayCutoutShortEdges | fail | junit.framework.AssertionFailedError: unexpected timeout | 复测pass |
| android.server.wm.LocationInWindowTests#testLocationInWindow_appWindow_fullscreen | fail | junit.framework.AssertionFailedError: unexpected timeout | 复测pass |
| android.server.wm.LocationInWindowTests#testLocationInWindow_floatingWindow | fail | junit.framework.AssertionFailedError: unexpected timeout | 复测pass |
| android.server.wm.LocationOnScreenTests#testLocationOnDisplay_appWindow | fail | junit.framework.AssertionFailedError: unexpected timeout | 复测pass |
| android.server.wm.LocationOnScreenTests#testLocationOnDisplay_appWindow_displayCutoutNever | fail | junit.framework.AssertionFailedError: unexpected timeout | 复测pass |
| android.server.wm.LocationOnScreenTests#testLocationOnDisplay_appWindow_displayCutoutShortEdges | fail | junit.framework.AssertionFailedError: unexpected timeout | 复测pass |
| android.server.wm.LocationOnScreenTests#testLocationOnDisplay_appWindow_fullscreen | fail | junit.framework.AssertionFailedError: unexpected timeout | 复测pass |
| android.server.wm.LocationOnScreenTests#testLocationOnDisplay_floatingWindow | fail | junit.framework.AssertionFailedError: unexpected timeout | 复测pass |
| arm64-v8a signed-CtsSecureElementAccessControlTestCases1 | |||
| Test | Result | Details | |
| android.omapi.accesscontrol1.cts.AccessControlTest#testAuthorizedAID | fail | java.lang.AssertionError: Unexpected Exception java.lang.SecurityException: Exception in setUpChannelAccess()java.security.AccessControlException: SecureElement-AccessControlEnforceraccess denied: No ARF exists | 特殊SIM 卡测试，如外网卡，白卡 |
| android.omapi.accesscontrol1.cts.AccessControlTest#testAuthorizedAPDUAID40 | fail | java.lang.AssertionError: Unexpected Exception java.lang.SecurityException: Exception in setUpChannelAccess()java.security.AccessControlException: SecureElement-AccessControlEnforceraccess denied: No ARF exists | 特殊SIM 卡测试，如外网卡，白卡 |
| android.omapi.accesscontrol1.cts.AccessControlTest#testAuthorizedAPDUAID41 | fail | java.lang.AssertionError: Unexpected Exception java.lang.SecurityException: Exception in setUpChannelAccess()java.security.AccessControlException: SecureElement-AccessControlEnforceraccess denied: No ARF exists | 特殊SIM 卡测试，如外网卡，白卡 |
| android.omapi.accesscontrol1.cts.AccessControlTest#testUnauthorisedAPDUAID40 | fail | java.lang.AssertionError: Unexpected Exception java.lang.SecurityException: Exception in setUpChannelAccess()java.security.AccessControlException: SecureElement-AccessControlEnforceraccess denied: No ARF exists | 特殊SIM 卡测试，如外网卡，白卡 |
| android.omapi.accesscontrol1.cts.AccessControlTest#testUnauthorisedAPDUAID41 | fail | java.lang.AssertionError: Unexpected Exception java.lang.SecurityException: Exception in setUpChannelAccess()java.security.AccessControlException: SecureElement-AccessControlEnforceraccess denied: No ARF exists | 特殊SIM 卡测试，如外网卡，白卡 |
| android.omapi.accesscontrol1.cts.AccessControlTest#testUnauthorizedAID | fail | java.lang.AssertionError | 特殊SIM 卡测试，如外网卡，白卡 |
| arm64-v8a signed-CtsSecureElementAccessControlTestCases2 | |||
| Test | Result | Details | |
| android.omapi.accesscontrol2.cts.AccessControlTest#testAuthorizedAID | fail | java.lang.AssertionError: Unexpected Exception java.lang.SecurityException: Exception in setUpChannelAccess()java.security.AccessControlException: SecureElement-AccessControlEnforceraccess denied: No ARF exists | 特殊SIM 卡测试，如外网卡，白卡 |
| android.omapi.accesscontrol2.cts.AccessControlTest#testAuthorizedAPDUAID40 | fail | java.lang.AssertionError: Unexpected Exception java.lang.SecurityException: Exception in setUpChannelAccess()java.security.AccessControlException: SecureElement-AccessControlEnforceraccess denied: No ARF exists | 特殊SIM 卡测试，如外网卡，白卡 |
| android.omapi.accesscontrol2.cts.AccessControlTest#testAuthorizedAPDUAID41 | fail | java.lang.AssertionError: Unexpected Exception java.lang.SecurityException: Exception in setUpChannelAccess()java.security.AccessControlException: SecureElement-AccessControlEnforceraccess denied: No ARF exists | 特殊SIM 卡测试，如外网卡，白卡 |
| android.omapi.accesscontrol2.cts.AccessControlTest#testUnauthorisedAPDUAID40 | fail | java.lang.AssertionError: Unexpected Exception java.lang.SecurityException: Exception in setUpChannelAccess()java.security.AccessControlException: SecureElement-AccessControlEnforceraccess denied: No ARF exists | 特殊SIM 卡测试，如外网卡，白卡 |
| android.omapi.accesscontrol2.cts.AccessControlTest#testUnauthorisedAPDUAID41 | fail | java.lang.AssertionError: Unexpected Exception java.lang.SecurityException: Exception in setUpChannelAccess()java.security.AccessControlException: SecureElement-AccessControlEnforceraccess denied: No ARF exists | 特殊SIM 卡测试，如外网卡，白卡 |
| android.omapi.accesscontrol2.cts.AccessControlTest#testUnauthorizedAID | fail | java.lang.AssertionError | 特殊SIM 卡测试，如外网卡，白卡 |
| arm64-v8a signed-CtsSecureElementAccessControlTestCases3 | |||
| Test | Result | Details | |
| android.omapi.accesscontrol3.cts.AccessControlTest#testAuthorizedAID | fail | java.lang.AssertionError: Unexpected Exception java.lang.SecurityException: Exception in setUpChannelAccess()java.security.AccessControlException: SecureElement-AccessControlEnforceraccess denied: No ARF exists | 特殊SIM 卡测试，如外网卡，白卡 |
| android.omapi.accesscontrol3.cts.AccessControlTest#testAuthorizedAPDUAID40 | fail | java.lang.AssertionError: Unexpected Exception java.lang.SecurityException: Exception in setUpChannelAccess()java.security.AccessControlException: SecureElement-AccessControlEnforceraccess denied: No ARF exists | 特殊SIM 卡测试，如外网卡，白卡 |
| android.omapi.accesscontrol3.cts.AccessControlTest#testAuthorizedAPDUAID41 | fail | java.lang.AssertionError: Unexpected Exception java.lang.SecurityException: Exception in setUpChannelAccess()java.security.AccessControlException: SecureElement-AccessControlEnforceraccess denied: No ARF exists | 特殊SIM 卡测试，如外网卡，白卡 |
| android.omapi.accesscontrol3.cts.AccessControlTest#testUnauthorisedAPDUAID41 | fail | java.lang.AssertionError: Unexpected Exception java.lang.SecurityException: Exception in setUpChannelAccess()java.security.AccessControlException: SecureElement-AccessControlEnforceraccess denied: No ARF exists | 特殊SIM 卡测试，如外网卡，白卡 |
| android.omapi.accesscontrol3.cts.AccessControlTest#testUnauthorizedAID | fail | java.lang.AssertionError | 特殊SIM 卡测试，如外网卡，白卡 |
更多相关文章
- Android(安卓)Wear创建通知的几种方式
- Android能够获取到唯一的设备ID吗?
- android单元测试
- 测试_Android通过tcpdump抓包
- 移动应用测试框架—Calabash Android(安卓)简介
- Android添加单元测试的方法与步骤
- android CTS测试
- Android触屏测试实例代码
- Become a better android developer(转载)