[CTS][GL]CtsNetTestCases fail 1 : run cts -m CtsNetTestCases -t android.net.cts.ApfIntegrationTest#testReadWriteProgram [387214978]

WAI

Bug

Status Update

No update yet.

Description

pe...@longcheer.corp-partner.google.com

created issue #1

Jan 2, 2025 07:51AM

Dear Google:
During the CTS test, the following exception will appear, check the log, there is a Process:

android.net (CtsNetTestCases.apk) process crash, please help to see what is the reason?

(The test report and bugreport have been uploaded to the nearby center, please check.)

Test Type: Execute XTS
Software Version: 0.0.7 VMUMIXM
Test tool: 15_r2/12699308
Testing device type: M84- European Union
Reproduce steps:run cts -m CtsNetTestCases -t android.net.cts.ApfIntegrationTest#testReadWriteProgram
Thanks
log:
行 20377: 01-02 14:04:18.734 10314 10206 10222 E TestRunner: failed: testReadWriteProgram(android.net.cts.ApfIntegrationTest)
行 20378: 01-02 14:04:18.735 10314 10206 10222 E TestRunner: ----- begin exception -----
行 20379: 01-02 14:04:18.735 10314 10206 10222 E TestRunner: expected not to be empty
行 20380: 01-02 14:04:18.735 10314 10206 10222 E TestRunner: at android.net.cts.ApfIntegrationTest.readProgram(ApfIntegrationTest.kt:370)
行 20381: 01-02 14:04:18.735 10314 10206 10222 E TestRunner: at android.net.cts.ApfIntegrationTest.testReadWriteProgram(ApfIntegrationTest.kt:400)
行 20382: 01-02 14:04:18.735 10314 10206 10222 E TestRunner: ----- end exception -----
行 20383: 01-02 14:04:18.737 10314 10206 10222 I TestRunner: finished: testReadWriteProgram(android.net.cts.ApfIntegrationTest)
行 20384: 01-02 14:04:18.737 10314 10206 10222 D ActivityThread: Too many transaction errors, throttling freezer binder callback.
行 20385: 01-02 14:04:18.744 10314 10206 10222 V CtsSystemUtil: Running command: input keyevent KEYCODE_WAKEUP
行 20386: 01-02 14:04:18.745 10314 10206 10222 D ActivityThread: Too many transaction errors, throttling freezer binder callback.
行 20387: 01-02 14:04:18.746 10314 10206 10222 E UiAutomation: Error executing shell command!
行 20388: 01-02 14:04:18.746 10314 10206 10222 E UiAutomation: android.os.DeadObjectException
行 20389: 01-02 14:04:18.746 10314 10206 10222 E UiAutomation: at android.os.BinderProxy.transactNative(Native Method)
行 20390: 01-02 14:04:18.746 10314 10206 10222 E UiAutomation: at android.os.BinderProxy.transact(BinderProxy.java:684)
行 20391: 01-02 14:04:18.746 10314 10206 10222 E UiAutomation: at android.app.IUiAutomationConnection$Stub$Proxy.executeShellCommandWithStderr(IUiAutomationConnection.java:824)
行 20392: 01-02 14:04:18.746 10314 10206 10222 E UiAutomation: at android.app.UiAutomation.executeShellCommandInternal(UiAutomation.java:1735)
行 20393: 01-02 14:04:18.746 10314 10206 10222 E UiAutomation: at android.app.UiAutomation.executeShellCommandRwe(UiAutomation.java:1695)
行 20394: 01-02 14:04:18.746 10314 10206 10222 E UiAutomation: at com.android.compatibility.common.util.SystemUtil.runShellCommandOrThrow(SystemUtil.java:144)
行 20395: 01-02 14:04:18.746 10314 10206 10222 E UiAutomation: at android.net.cts.ApfIntegrationTest$Companion.turnScreenOn(ApfIntegrationTest.kt:149)
行 20396: 01-02 14:04:18.746 10314 10206 10222 E UiAutomation: at android.net.cts.ApfIntegrationTest$Companion.tearDownOnce(ApfIntegrationTest.kt:181)
行 20397: 01-02 14:04:18.746 10314 10206 10222 E UiAutomation: at android.net.cts.ApfIntegrationTest.tearDownOnce(Unknown Source:2)
行 20398: 01-02 14:04:18.746 10314 10206 10222 E UiAutomation: at java.lang.reflect.Method.invoke(Native Method)
行 20399: 01-02 14:04:18.746 10314 10206 10222 E UiAutomation: at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:59)
行 20400: 01-02 14:04:18.746 10314 10206 10222 E UiAutomation: at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
行 20401: 01-02 14:04:18.746 10314 10206 10222 E UiAutomation: at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:61)
行 20402: 01-02 14:04:18.746 10314 10206 10222 E UiAutomation: at org.junit.internal.runners.statements.RunAfters.invokeMethod(RunAfters.java:46)
行 20403: 01-02 14:04:18.746 10314 10206 10222 E UiAutomation: at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:33)
行 20404: 01-02 14:04:18.746 10314 10206 10222 E UiAutomation: at org.junit.runners.ParentRunner$3.evaluate(ParentRunner.java:306)
行 20405: 01-02 14:04:18.746 10314 10206 10222 E UiAutomation: at org.junit.runners.ParentRunner.run(ParentRunner.java:413)
行 20406: 01-02 14:04:18.746 10314 10206 10222 E UiAutomation: at androidx.test.ext.junit.runners.AndroidJUnit4.run(AndroidJUnit4.java:162)
行 20407: 01-02 14:04:18.746 10314 10206 10222 E UiAutomation: at com.android.testutils.DevSdkIgnoreRunner$RunnerWrapper.run(DevSdkIgnoreRunner.kt:73)
行 20408: 01-02 14:04:18.746 10314 10206 10222 E UiAutomation: at com.android.testutils.DevSdkIgnoreRunner.run(DevSdkIgnoreRunner.kt:153)
行 20409: 01-02 14:04:18.746 10314 10206 10222 E UiAutomation: at org.junit.runners.Suite.runChild(Suite.java:128)
行 20410: 01-02 14:04:18.746 10314 10206 10222 E UiAutomation: at org.junit.runners.Suite.runChild(Suite.java:27)
行 20411: 01-02 14:04:18.746 10314 10206 10222 E UiAutomation: at org.junit.runners.ParentRunner$4.run(ParentRunner.java:331)
行 20412: 01-02 14:04:18.746 10314 10206 10222 E UiAutomation: at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:79)
行 20413: 01-02 14:04:18.746 10314 10206 10222 E UiAutomation: at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:329)
行 20414: 01-02 14:04:18.746 10314 10206 10222 E UiAutomation: at org.junit.runners.ParentRunner.-$$Nest$mrunChildren(Unknown Source:0)
行 20415: 01-02 14:04:18.746 10314 10206 10222 E UiAutomation: at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:293)
行 20416: 01-02 14:04:18.746 10314 10206 10222 E UiAutomation: at org.junit.runners.ParentRunner$3.evaluate(ParentRunner.java:306)
行 20417: 01-02 14:04:18.746 10314 10206 10222 E UiAutomation: at org.junit.runners.ParentRunner.run(ParentRunner.java:413)
行 20418: 01-02 14:04:18.746 10314 10206 10222 E UiAutomation: at org.junit.runner.JUnitCore.run(JUnitCore.java:137)
行 20419: 01-02 14:04:18.746 10314 10206 10222 E UiAutomation: at org.junit.runner.JUnitCore.run(JUnitCore.java:115)
行 20420: 01-02 14:04:18.746 10314 10206 10222 E UiAutomation: at androidx.test.internal.runner.TestExecutor.execute(TestExecutor.java:68)
行 20421: 01-02 14:04:18.746 10314 10206 10222 E UiAutomation: at androidx.test.internal.runner.TestExecutor.execute(TestExecutor.java:59)
行 20422: 01-02 14:04:18.746 10314 10206 10222 E UiAutomation: at androidx.test.runner.AndroidJUnitRunner.onStart(AndroidJUnitRunner.java:463)
行 20423: 01-02 14:04:18.746 10314 10206 10222 E UiAutomation: at android.app.Instrumentation$InstrumentationThread.run(Instrumentation.java:2634)
行 20710: 01-02 14:04:20.785 10314 10206 10222 E TestRunner: failed: android.net.cts.ApfIntegrationTest
行 20711: 01-02 14:04:20.785 10314 10206 10222 E TestRunner: ----- begin exception -----
行 20712: 01-02 14:04:20.785 10314 10206 10222 E TestRunner: expected to be true
行 20713: 01-02 14:04:20.785 10314 10206 10222 E TestRunner: at android.net.cts.ApfIntegrationTest$Companion.turnScreenOn(ApfIntegrationTest.kt:151)
行 20714: 01-02 14:04:20.785 10314 10206 10222 E TestRunner: at android.net.cts.ApfIntegrationTest$Companion.tearDownOnce(ApfIntegrationTest.kt:181)
行 20715: 01-02 14:04:20.785 10314 10206 10222 E TestRunner: at android.net.cts.ApfIntegrationTest.tearDownOnce(Unknown Source:2)
行 20716: 01-02 14:04:20.785 10314 10206 10222 E TestRunner: ----- end exception -----
行 20717: 01-02 14:04:20.807 10314 10206 10222 I TestRunner: run finished: 1 tests, 2 failed, 0 ignored
行 20718: 01-02 14:04:20.813 10314 10206 10222 D ActivityThread: Too many transaction errors, throttling freezer binder callback.
行 20720: 01-02 14:04:20.815 10314 10206 10222 E AndroidRuntime: FATAL EXCEPTION: Instr: androidx.test.runner.AndroidJUnitRunner
行 20721: 01-02 14:04:20.815 10314 10206 10222 E AndroidRuntime: Process: android.net.cts, PID: 10206
行 20722: 01-02 14:04:20.815 10314 10206 10222 E AndroidRuntime: java.lang.RuntimeException: Error while disconnecting UiAutomation@d0fc39b[id=-1, displayId=0, flags=0]
行 20723: 01-02 14:04:20.815 10314 10206 10222 E AndroidRuntime: at android.app.UiAutomation.disconnect(UiAutomation.java:455)
行 20724: 01-02 14:04:20.815 10314 10206 10222 E AndroidRuntime: at android.app.Instrumentation.finish(Instrumentation.java:288)
行 20725: 01-02 14:04:20.815 10314 10206 10222 E AndroidRuntime: at androidx.test.runner.MonitoringInstrumentation.finish(MonitoringInstrumentation.java:409)
行 20726: 01-02 14:04:20.815 10314 10206 10222 E AndroidRuntime: at androidx.test.runner.AndroidJUnitRunner.onStart(AndroidJUnitRunner.java:474)
行 20727: 01-02 14:04:20.815 10314 10206 10222 E AndroidRuntime: at android.app.Instrumentation$InstrumentationThread.run(Instrumentation.java:2634)
行 20728: 01-02 14:04:20.815 10314 10206 10222 E AndroidRuntime: Caused by: android.os.DeadObjectException
行 20729: 01-02 14:04:20.815 10314 10206 10222 E AndroidRuntime: at android.os.BinderProxy.transactNative(Native Method)
行 20730: 01-02 14:04:20.815 10314 10206 10222 E AndroidRuntime: at android.os.BinderProxy.transact(BinderProxy.java:684)
行 20731: 01-02 14:04:20.815 10314 10206 10222 E AndroidRuntime: at android.app.IUiAutomationConnection$Stub$Proxy.disconnect(IUiAutomationConnection.java:540)
行 20732: 01-02 14:04:20.815 10314 10206 10222 E AndroidRuntime: at android.app.UiAutomation.disconnect(UiAutomation.java:453)
行 20733: 01-02 14:04:20.815 10314 10206 10222 E AndroidRuntime: ... 4 more

CtsNetTestCases.zip

Restricted

50 MB

Download

Comments

vi...@google.com <vi...@google.com> Jan 2, 2025 12:45PM

Assigned to vi...@google.com.

vi...@google.com <vi...@google.com> #2Jan 2, 2025 04:27PM

We have shared this with our product and engineering team and will update this issue with more information as it becomes available.

pe...@longcheer.corp-partner.google.com <pe...@longcheer.corp-partner.google.com> #3Jan 3, 2025 01:55AM

Dear qcom：

This issue is quite urgent. Please help us analyze it first.

Thanks！

pe...@longcheer.corp-partner.google.com <pe...@longcheer.corp-partner.google.com> #4Jan 6, 2025 08:01AM

Dear google：

any update？This issue is quite urgent. Please help us analyze it first.

thanks

yu...@google.com <yu...@google.com> #5Jan 6, 2025 12:59PM

Hi pengtiancheng

The testReadWriteProgram() fails to indicate the APF implementation in the DUT is not fully followed what is required in VSR.

https://docs.partner.android.com/gms/policies/domains/reqs

行 20377: 01-02 14:04:18.734 10314 10206 10222 E TestRunner: failed: testReadWriteProgram(android.net.cts.ApfIntegrationTest)
        行 20378: 01-02 14:04:18.735 10314 10206 10222 E TestRunner: ----- begin exception -----
        行 20379: 01-02 14:04:18.735 10314 10206 10222 E TestRunner: expected not to be empty
        行 20380: 01-02 14:04:18.735 10314 10206 10222 E TestRunner:     at android.net.cts.ApfIntegrationTest.readProgram(ApfIntegrationTest.kt:370)

This log suggest the APF Wi-Fi HAL is not correctly implemented.

https://cs.android.com/android/platform/superproject/main/+/main:hardware/interfaces/wifi/aidl/aidl_api/android.hardware.wifi/current/android/hardware/wifi/IWifiStaIface.aidl;l=51?q=f:aidl%20readApf&ss=android%2Fplatform%2Fsuperproject%2Fmain

Please confirm with your chipset vendors.

Thanks,

Yuyang

pe...@longcheer.corp-partner.google.com <pe...@longcheer.corp-partner.google.com> #6Jan 7, 2025 02:41AM

Dear Yuyang：

However, the log below shows that there seems to be a timeout problem with adb, resulting in the failure of executing the shell command. Can you help me find the specific reason? If you need more detailed log, please let me know.

01-02 14:04:18.522 10314 10206 10332 V CtsSystemUtil: Running command: cmd network_stack apf wlan0 read
01-02 14:04:18.607 shell 16337 16337 W adbd : timeout expired while flushing socket, closing

01-02 14:04:18.718 10314 10206 10222 V CtsSystemUtil: Running command: cmd network_stack apf wlan0 resume
01-02 14:04:18.720 1000 1773 4812 W ActivityManager: pid 10206 android.net.cts sent binder code 13 with flags 2 to frozen apps and got error -32
01-02 14:04:18.721 1000 1773 4812 D ActivityManager: Too many transaction errors, throttling freezer binder callback.
01-02 14:04:18.727 10314 10206 10222 E UiAutomation: Error executing shell command!
01-02 14:04:18.727 10314 10206 10222 E UiAutomation: android.os.DeadObjectException

thanks

re...@longcheer.corp-partner.google.com <re...@longcheer.corp-partner.google.com> #7Jan 8, 2025 09:00AM

Comment has been deleted.

Message last modified on Jan 8, 2025 09:00AM

re...@longcheer.corp-partner.google.com <re...@longcheer.corp-partner.google.com> #8Jan 8, 2025 09:02AM

The Qualcomm mentioned they have got an waive in https://partnerissuetracker.corp.google.com/issues/364538054#comment48 We don't have permission to see this list。 For our project,the fail is run cts -m CtsNetTestCases -t android.net.cts.ApfIntegrationTest#testReadWriteProgram fail reason: "Test failed to run to completion. Reason: 'Failed to receive adb shell test output within 600000 ms. Test may have timed out, or adb connection to device became unresponsive'. Check device logcat for details"

Could you help us to check whether the following item is in the new approved list?
Or please attach the new approved list here in b/364538054. Thank you!

yu...@google.com <yu...@google.com> #9Jan 8, 2025 09:12AM

The Qualcomm mentioned they have got an waive in https://partnerissuetracker.corp.google.com/issues/364538054#comment48 We don't have permission to see this list。

This testReadWriteProgram doesn't have wavier, therefore this CTS MUST pass.

Reason: 'Failed to receive adb shell test output within 600000 ms. Test may have timed out, or adb connection to device became unresponsive'

This failure seems due to a known issue. The issue is fixed by https://r.android.com/3426236. Could you please get the latest CTS test suits and test it again.

Thanks,

Yuyang

re...@longcheer.corp-partner.google.com <re...@longcheer.corp-partner.google.com> #10Jan 8, 2025 01:41PM

Thanks for your precious information, we have passed it on the today's CTS suits. Thank you very much! :)

vi...@google.com <vi...@google.com> #11Jan 23, 2025 10:15AM

Status: Won't Fix (Intended Behavior)

We are closing this issue based on above comment, Thanks