IssueTracker

Project: platform/frameworks/support
Branch: androidx-main
Author: Radha Nakade <radhanakade@google.com>
Link:      https://android-review.googlesource.com/3510337

Migrate traffic from pixel2 to mediumphone on FTL emulators.

Migrate traffic from pixel2 to mediumphone on FTL emulators. 
 
Bug: 396715333 
 
Test: ./gradlew emoji2:emoji2-emojipicker:ftlmediumphoneapi33 
Change-Id: If5555443ca1a91479128e1bd6f4f909154c40ba2

> Task :paging:paging-common:jsBrowserTest
Disconnected (0 times) reconnect failed before timeout of 35000ms (ping timeout)

This seems to imply Karma timing out while running tests again, after increasing the load with the addition of Paging. I'm able to reproduce locally by just running ./gradlew paging:paging-common:jsBrowserTest.

I'm having trouble getting a build scan to upload, but it definitely runs the tests for 35 seconds locally then timeout.

Hi Omar, yes I can reproduce it locally with the linked CL by running ./gradlew :paging:paging-common:jsBrowserTest. --debug shows a bit more info, not sure if relevant

2025-02-13T10:40:10.880-0800 [DEBUG] [org.jetbrains.kotlin.gradle.tasks.testing] [KOTLIN] TCSM: ##TC[message text='13 02 2025 10:40:10.815:WARN |[Chrome Headless 130.0.6723.31 (Mac OS 10.15.7)|]: Disconnected (0 times) reconnect failed before timeout of 35000ms (ping timeout)' type='WARN']
2025-02-13T10:40:10.880-0800 [WARN] [org.jetbrains.kotlin.gradle.tasks.testing] Disconnected (0 times) reconnect failed before timeout of 35000ms (ping timeout)
2025-02-13T10:40:10.880-0800 [DEBUG] [org.jetbrains.kotlin.gradle.tasks.testing] [KOTLIN] TCSM stdout captured: Chrome Headless 130.0.6723.31 (Mac OS 10.15.7) ERROR

2025-02-13T10:40:10.881-0800 [DEBUG] [org.jetbrains.kotlin.gradle.tasks.testing] Chrome Headless 130.0.6723.31 (Mac OS 10.15.7) ERROR
2025-02-13T10:40:10.881-0800 [DEBUG] [org.jetbrains.kotlin.gradle.tasks.testing] [KOTLIN] TCSM stdout captured:   Disconnected reconnect failed before timeout of 35000ms (ping timeout)

I pulled the change (aosp/3413761) and Im getting errors in compilation:

> Task :paging:paging-common:compileKotlinJs FAILED
e: file:///Users/omarismail/Desktop/androidx-main/frameworks/support/paging/paging-common/src/commonMain/kotlin/androidx/paging/PagingDataPresenter.kt:506:9 JavaScript name (retry) generated for this declaration clashes with another declaration: fun retry(): Unit
e: file:///Users/omarismail/Desktop/androidx-main/frameworks/support/paging/paging-common/src/commonMain/kotlin/androidx/paging/PagingDataPresenter.kt:507:9 JavaScript name (refresh) generated for this declaration clashes with another declaration: fun refresh(): Unit
e: file:///Users/omarismail/Desktop/androidx-main/frameworks/support/paging/paging-common/src/commonMain/kotlin/androidx/paging/PagingDataPresenter.kt:509:9 JavaScript name (retry) generated for this declaration clashes with another declaration: var retry: Boolean
e: file:///Users/omarismail/Desktop/androidx-main/frameworks/support/paging/paging-common/src/commonMain/kotlin/androidx/paging/PagingDataPresenter.kt:513:9 JavaScript name (refresh) generated for this declaration clashes with another declaration: var refresh: Boolean

can you please rebase your change on aosp/androidx-main so that there is no merge conflict in the change?

Resolved compile errors. You should be able to run it locally now.

Edit: Looking into resolution errors on presubmit - its not present locally

Thanks! I pulled the change and can replicate the test timeout locally. However, if I 10x the timeout to 5 minutes (buildSrc/karmaconfig/karma.conf.js), I am still getting the timeout.

The source of the issue is coming from some of the tests in (paging/paging-common/src/commonTest/kotlin/androidx/paging/PagingDataPresenterTest.kt). I have commented out the tests that are causing the timeout and uploaded them to aosp/3494658.

From the commented out code, I then started to see what might be causing the issue. I ran the only test that does not call the custom runTest function (remoteRefresh_refreshStatePersists) and by bi-section, it seems like presenter.refresh() causes the timeout. When I comment that line, the test runs and fails as expected, but at least it does not hang.

Re-assigning back to Clara as the issue does not seem to be infra-related