android / android/nowinandroid
[Bug]: navigationBar_multipleBackStackInterests might be flaky
- Dominant language
- Kotlin
- Stars
- 21.8k
- Forks
- 4.6k
- Avg merge
- 19h 20m
- Merged PRs (30d)
- 2
Description
### Is there an existing issue for this?
- [X] I have searched the existing issues
### Is there a StackOverflow question about this issue?
- [X] I have searched StackOverflow
### What happened?
navigationBar_multipleBackStackInterests might be flaky. It tends to fail in API 30.
Example failure:
https://github.com/android/nowinandroid/actions/runs/6774060182/job/18410826425
Related: #1011
### Relevant logcat output
```shell
> Task :app:connectedDemoDebugAndroidTest
Starting 26 tests on test(AVD) - 11
> Task :core:database:connectedDemoDebugAndroidTest
> Task :app:connectedDemoDebugAndroidTest
com.google.samples.apps.nowinandroid.ui.NavigationTest > navigationBar_multipleBackStackInterests[test(AVD) - 11] FAILED
kotlinx.coroutines.test.UncompletedCoroutinesError: After waiting for 10s, the test coroutine is not completing
at kotlinx.coroutines.test.TestBuildersKt__TestBuildersKt$runTest$2$1$2$1.invoke(TestBuilders.kt:349)
[DDMLIB]: An unexpected packet was received before the handshake.
```
### Code of Conduct
- [X] I agree to follow this project's Code of Conduct
Contributor guide
Research direction
Start with NavigationTest and the navigationBar_multipleBackStackInterests test, then inspect the linked API 30 Actions run and the related issue #1011. Reproduce the failure on the test(AVD) - 11 configuration and trace the kotlinx.coroutines.test timeout and DDMLIB handshake output. Done means the test no longer flakes on API 30 and the instrumentation run completes reliably.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, kotlin
- Domain
- mobile, testing
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100