-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
Flaky test turned CI bot red #44352
Comments
Another case happened on https://ci.chromium.org/p/dart/builders/ci.sandbox/app-kernel-linux-release-x64/10130 build, where the bot turned red due to failure |
Happened once again - Failures:
They passed during deflaking:
|
I suspect this may have to do with my rewrite of the logic that marks a flaky record as active: false when it is forgiven, and sets it to active: true when flakiness is seen again. The test with the problem does have an inactive flaky record, and it is not being set to active again, and the timeout seen from the original run (not the deflaking runs) is not being stored in the flaky record. |
vm-kernel-nnbd-linux-release-x64
bot turned red at https://ci.chromium.org/p/dart/builders/ci.sandbox/vm-kernel-nnbd-linux-release-x64/3109 due toDeflaking log says the test passed 5 times:
@whesse @athomas Why that particular one-time failure turned bot red? Are we not filtering flaky test failures anymore?
The text was updated successfully, but these errors were encountered: