-
Notifications
You must be signed in to change notification settings - Fork 27.3k
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
[video_player] integration test is very flaky on iOS #86915
Comments
This is definitely still a common source of flake. The assertion that is failing is: |
These tests are failing frequently, and interfering with the tree staying open. Tracking issues: flutter/flutter#88837 flutter/flutter#86915 flutter/flutter#86757
These tests are failing frequently, and interfering with the tree staying open. Tracking issues: flutter/flutter#88837 flutter/flutter#86915 flutter/flutter#86757
These tests are failing frequently, and interfering with the tree staying open. Tracking issues: flutter/flutter#88837 flutter/flutter#86915 flutter/flutter#86757
These tests are failing frequently, and interfering with the tree staying open. Tracking issues: flutter/flutter#88837 flutter/flutter#86915 flutter/flutter#86757
These tests are failing frequently, and interfering with the tree staying open. Tracking issues: flutter/flutter#88837 flutter/flutter#86915 flutter/flutter#86757
These tests are failing frequently, and interfering with the tree staying open. Tracking issues: flutter/flutter#88837 flutter/flutter#86915 flutter/flutter#86757
These tests are failing frequently, and interfering with the tree staying open. Tracking issues: flutter/flutter#88837 flutter/flutter#86915 flutter/flutter#86757
This issue is marked P1 but has had no recent status updates. The P1 label indicates high-priority issues that are at the top of the work list. This is the highest priority level a bug can have if it isn't affecting a top-tier customer or breaking the build. Bugs marked P1 are generally actively being worked on unless the assignee is dealing with a P0 bug (or another P1 bug). Issues at this level should be resolved in a matter of months and should have monthly updates on GitHub. Please consider where this bug really falls in our current priorities, and label it or assign it accordingly. This allows people to have a clearer picture of what work is actually planned. Thanks! |
We should reenable this to see if it's still flaky. |
I just saw this flake on Android. Maybe there's an issue with the test design. Edit: looking at this test again, I don't actually see anything here that waits for it to start. It waits for animation to finish, but I don't see any reason to expect that would happen only after the video has loaded. I'm going to rework this and try re-enabling it. |
This attempts to address two sources of flake: - A test that playing doesn't continue past the duration flakily fails, at least on Android, with a position a small amount past the duration. This seems like an unexpected library behavior that we wouldn't want to expose to clients, so rather than change the test, this makes the logic that updates the `Value` clamp the position to the duration. - A test that asset videos play has been restructured to actually wait for the future that should start playing to complete before checking whether it's playing. The test was previously not actually waiting for anything other than animations to complete, and there's no reason the placeholder layout couldn't have completed before the asset loaded. The fact that the test was already disabled for iOS is strong evidence that the flake we are seeing on Android is a problem with the test itself, so hopefully this addresses both platforms. Fixes flutter/flutter#86915
This attempts to address two sources of flake: - A test that playing doesn't continue past the duration flakily fails, at least on Android, with a position a small amount past the duration. This seems like an unexpected library behavior that we wouldn't want to expose to clients, so rather than change the test, this makes the logic that updates the `Value` clamp the position to the duration. - A test that asset videos play has been restructured to actually wait for the future that should start playing to complete before checking whether it's playing. The test was previously not actually waiting for anything other than animations to complete, and there's no reason the placeholder layout couldn't have completed before the asset loaded. The fact that the test was already disabled for iOS is strong evidence that the flake we are seeing on Android is a problem with the test itself, so hopefully this addresses both platforms. Fixes flutter/flutter#86915
This attempts to address two sources of flake: - A test that playing doesn't continue past the duration flakily fails, at least on Android, with a position a small amount past the duration. This seems like an unexpected library behavior that we wouldn't want to expose to clients, so rather than change the test, this makes the logic that updates the `Value` clamp the position to the duration. - A test that asset videos play has been restructured to actually wait for the future that should start playing to complete before checking whether it's playing. The test was previously not actually waiting for anything other than animations to complete, and there's no reason the placeholder layout couldn't have completed before the asset loaded. The fact that the test was already disabled for iOS is strong evidence that the flake we are seeing on Android is a problem with the test itself, so hopefully this addresses both platforms. Fixes flutter/flutter#86915
This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of |
Recently we're having to re-run the build-ipas+drive_examples shard that contains the video_player plugin pretty frequently. I haven't gone back through logs, but I feel like it's been the last week or so where it's been really bad.
Example failing run: https://cirrus-ci.com/task/4561521528274944
The text was updated successfully, but these errors were encountered: