-
Notifications
You must be signed in to change notification settings - Fork 26.8k
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 customer_testing is 2.00% flaky #149230
Comments
One of these is the same analyzer crash as also seen on Mac: #149231 (comment) |
[prod pool] flaky ratio for the past (up to) 100 commits between 2024-05-28 and 2024-06-04 is 1.00%. Flaky number: 1; total number: 100. Recent test runs: |
The analyhzer crash seems to be gone. The new failure is a timeout in the zulip tests:
|
cc @gnprice for zulip |
Thanks. We've seen that flake a handful of times before: Then I believe that's the only known flaky test in the zulip-flutter repo. (Though I suppose if we have any really low-frequency flakes, then flutter/tests may be what eventually causes us to notice them!) |
Fixes flutter/flutter#149230. This pulls in: zulip/zulip-flutter@e85d6c5 zulip/zulip-flutter#726
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 customer_testing
had a flaky ratio 2.00% 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%20customer_testing/19403
Commit: 73fb6c7
Flaky builds:
https://ci.chromium.org/ui/p/flutter/builders/prod/Linux%20customer_testing/19403
https://ci.chromium.org/ui/p/flutter/builders/prod/Linux%20customer_testing/19364
Recent test runs:
https://flutter-dashboard.appspot.com/#/build?taskFilter=Linux%20customer_testing
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: