-
Notifications
You must be signed in to change notification settings - Fork 863
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
test: Attempt to fix flaky tests for Windows & Android #1441
Conversation
How debugging this feels like: |
Hmm seems like windows does not support IntegrationTestPlugin with captureScreenshot: https://github.com/flutter/flutter/blob/master/packages/integration_test/integration_test_macos/pubspec.yaml |
This only happens if GH is on its limits and takes longer than expected for some tasks... 😪 Very flaky, but hope to fix it some day. |
Maybe due to: actions/runner-images#7320 |
# Conflicts: # packages/audioplayers/example/integration_test/lib_test.dart
# Conflicts: # .github/workflows/test.yml # packages/audioplayers/example/integration_test/app/tabs/controls_tab.dart # packages/audioplayers/example/integration_test/app_test.dart
…/bluefireteam/audioplayers into gustl22/increase-timeout-windows
Still not fixed according to https://github.com/bluefireteam/audioplayers/actions/runs/6110536581/job/16584118505 |
# Description The tests in Windows & Android are possibly flaky for this reason: - In general it is not tested, if a source starts to play for app tests. - In the app test for `ReleaseMode.loop`, the source starts to play, but never completes or stops. See: https://github.com/bluefireteam/audioplayers/blob/fe81f3b1e600fe005febbe7cd3da02735a3de004/packages/audioplayers/example/integration_test/app/tabs/controls_tab.dart#L104 . This is now checked by getting the current position. The solution to the problem also raises another issue on Android, as the position can not be retrieved on very short sources, thus they are excluded from these tests and it is expected to make it work with Exoplayer (#1526). (cherry picked from commit c5b0b6e)
# Description The tests in Windows & Android are possibly flaky for this reason: - In general it is not tested, if a source starts to play for app tests. - In the app test for `ReleaseMode.loop`, the source starts to play, but never completes or stops. See: https://github.com/bluefireteam/audioplayers/blob/fe81f3b1e600fe005febbe7cd3da02735a3de004/packages/audioplayers/example/integration_test/app/tabs/controls_tab.dart#L104 . This is now checked by getting the current position. The solution to the problem also raises another issue on Android, as the position can not be retrieved on very short sources, thus they are excluded from these tests and it is expected to make it work with Exoplayer (#1526).
Description
The tests in Windows & Android are possibly flaky for this reason:
ReleaseMode.loop
, the source starts to play, but never completes or stops. See:audioplayers/packages/audioplayers/example/integration_test/app/tabs/controls_tab.dart
Line 104 in fe81f3b
The solution to the problem also raises another issue on Android, as the position can not be retrieved on very short sources, thus they are excluded from these tests and it is expected to make it work with Exoplayer (#1526).
Sometimes CI fails, cause Windows needs a long time to finish playing a source with lengths< 2s
.See: https://github.com/bluefireteam/audioplayers/actions/runs/4455910532/jobs/7826010863
This increases the timeout, so
onComplete
should be called in that time slot.audioplayers/packages/audioplayers/test/audioplayers_test.dart
Line 125 in 8babb0e
Checklist
fix:
,feat:
,docs:
,chore:
etc).///
, where necessary.Breaking Change
Related Issues
https://github.com/bluefireteam/audioplayers/actions/workflows/test.yml?query=branch%3Agustl22%2Fincrease-timeout-windows