-
Notifications
You must be signed in to change notification settings - Fork 26.9k
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
Linux web_long_running_tests_2_5 is 2.04% flaky #143834
Comments
No update yet. Just started tracking this yesterday. |
Still no update. |
[prod pool] flaky ratio for the past (up to) 100 commits between 2024-02-28 and 2024-03-05 is 0.00%. Flaky number: 0; total number: 100. |
I haven't made any progress on this. |
[prod pool] flaky ratio for the past (up to) 100 commits between 2024-03-05 and 2024-03-12 is 2.02%. Flaky number: 2; total number: 99. Recent test runs: |
Possibly due to #109474 ? The test just times out while trying to connect |
[prod pool] flaky ratio for the past (up to) 100 commits between 2024-03-13 and 2024-03-19 is 1.01%. Flaky number: 1; total number: 99. Recent test runs: |
This has gotten even more flaky lately. It seems to always flake on |
[prod pool] flaky ratio for the past (up to) 100 commits between 2024-03-19 and 2024-03-26 is 3.06%. Flaky number: 3; total number: 98. Recent test runs: |
Continuing to investigate this issue. The cause is still unknown. |
[prod pool] flaky ratio for the past (up to) 100 commits between 2024-03-27 and 2024-04-02 is 1.01%. Flaky number: 1; total number: 99. Recent test runs: |
I seem to be reproducing this now locally, so I have a bit more info to share. For one thing, I believe these flakes seem to only happen when running My repro steps are as follows:
This doesn't reproduce 100% of the time, but it doesn't usually take more than a couple of tries and the browser will stall. You can look in the JS console when this happens, and there is usually some sort of error related to module loading. Here is one such example:
The stacks seem to vary across different repros, but it always appears to be some sort of issue with module loading. It usually appears that the JavaScript assumes that some other script has run and has set some global state. |
[prod pool] flaky ratio for the past (up to) 100 commits between 2024-04-03 and 2024-04-09 is 0.00%. Flaky number: 0; total number: 94. |
[prod pool] flaky ratio for the past (up to) 100 commits between 2024-04-08 and 2024-04-16 is 0.00%. Flaky number: 0; total number: 98. |
It seems these flakes migrated into #146877. Deduping. |
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 |
The post-submit test builder
Linux web_long_running_tests_2_5
had a flaky ratio 2.04% for the past (up to) 100 commits, which is above our 2.00% threshold.One recent flaky example for a same commit: https://ci.chromium.org/ui/p/flutter/builders/prod/Linux%20web_long_running_tests_2_5/14957
Commit: fe4ab13
Flaky builds:
https://ci.chromium.org/ui/p/flutter/builders/prod/Linux%20web_long_running_tests_2_5/14957
https://ci.chromium.org/ui/p/flutter/builders/prod/Linux%20web_long_running_tests_2_5/14953
Recent test runs:
https://flutter-dashboard.appspot.com/#/build?taskFilter=Linux%20web_long_running_tests_2_5
Please follow https://github.com/flutter/flutter/wiki/Reducing-Test-Flakiness#fixing-flaky-tests to fix the flakiness and enable the test back after validating the fix (internal dashboard to validate: go/flutter_test_flakiness).
The text was updated successfully, but these errors were encountered: