Scenario app is still very flaky on CI #145988
Description
Possible leads:
-
Try reproducing on a Linux emulator:
# Setup and run Android 34 emulator. # ... # Run indefinitely until it fails. $ testing/scenario_app/tool/deflake_android_tests.sh
-
Consider adding
adb screenrecordto get visual output of what is failing.
Run and recordadb shell screenrecordduring Android scenario app engine#51832 -
Look into the emulator configuration in CI (
android_34_google_apis_x64.textpb) for ideas. -
Do not do output file comparisons when the test will fail anyway (gives false negatives)
Never panic infinally { ... }, check output logs on success only. engine#51814
For example, but also full list:
Every single one of these failures is due to a timeout that looks something like this:
03-29 06:41:21.667 [I] TestRunner: started: testRotatedMediaSurface_180(dev.flutter.scenariosui.ExternalTextureTests)
03-29 06:41:22.318 [I] flutter: Loading scenario display_texture
03-29 06:41:22.427 [W] Scenarios: Presenting frame 0
03-29 06:41:23.394 [W] ActivityManager: Unable to start service Intent { act=com.google.android.gms.drive.ApiService.RESET_AFTER_BOOT flg=0x4 cmp=com.google.android.gms/.drive.api.ApiService (has extras) } U=0: not found
03-29 06:41:24.177 [W] System: ClassLoader referenced unknown path:
03-29 06:41:24.250 [W] WindowOnBackDispatcher: sendCancelIfRunning: isInProgress=falsecallback=android.view.ViewRootImpl$$ExternalSyntheticLambda17@cbeae07
03-29 06:41:24.782 [I] Choreographer: Skipped 34 frames! The application may be doing too much work on its main thread.
03-29 06:41:24.903 [W] FlutterJNI: Tried to send a platform message response, but FlutterJNI was detached from native C++. Could not send. Response ID: 5
03-29 06:41:25.183 [I] flutter: Loading scenario display_texture
03-29 06:41:25.575 [W] Scenarios: Presenting frame 0
...
03-29 06:50:18.252 [I] ActivityManager: Killing 1889:com.google.android.apps.youtube.music/u0a147 (adj 955): empty #17The specific test case is not stable, though it's always a display_texture scenario that proceeds.
Notably, the full logs also seem to be missing, which is weird:
