7.0 CTS fail 项分析之google Issue （二）

CTS 7.0_r3

1、CtsDragAndDropHostTestCases下android.wm.cts.CrossAppDragAndDropTests#testCancelSoon等多条fail
fail log:junit.framework.AssertionFailedError: Missing DROP
用Google bug id: 30751444申请豁免

2、android.security.cts.ListeningPortsTest#testNoRemotelyAccessibleListeningTcp6Ports
      android.security.cts.ListeningPortsTest#testNoRemotelyAccessibleListeningUdp6Ports
用Google bug id:30490560申请豁免

3、android.telecom.cts.VideoCallTest#testReceiveSessionModifyResponse

junit.framework.AssertionFailedError: Session modify response should match expected. expected: but was: 
分析：google issue,test case did not give enough time to do preparation work

4、og.apache.harmony.crypto.tests.javax.crypto.interfaces.DHPublicKeyTest#test_getParams

Test failed to run to completion. Reason: 'Instrumentation run failed due to 'Process crashed.''. Check device logcat for details seldom issue,cts test case限制執行時間只有5 min，test case执行时间不固定
用bug id is 30858870申请豁免

5、android.backup.cts.BackupQuotaTest#testQuotaExceeded

java.io.IOException: read failed: EBADF (Bad file descriptor)

请用Google Issue Id: 30999937申请豁免

6、android.assist.cts.DisableContextTest#testContextAndScreenshotOff 

junit.framework.AssertionFailedError: Should not have been null - AssistContent: null

用Google bug id is 30859355申请豁免