-
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 pkg/analyzer_plugin/tool/spec/check_all_test #29134
Comments
@devoncarew I suspect that this is a result of adding formatting to the generation process, though I'm not sure why that would cause problems. |
We need to remember to revert https://codereview.chromium.org/2765273002/ when this is fixed (there won't be a failure). |
We need to also revert https://codereview.chromium.org/2768803002/. |
This is why issue 29133 says "Please update the expectations of these tests, and then re-enable them in pkg/pkg.status." in its second sentence. All issues that are listed in lines in the status file should have comments in the issue saying which status files were changed, and need to be reverted when the issue is fixed. Reopening 29133 because it lists the two other tests that are failing. |
But this issue has more useful information in it! |
I have no idea if something was fixed, but given that we guessed that it is caused by formatting, maybe things are changed enough that it is not flaky anymore. I will revert, or a gardener can revert, if it is still flaky. R=brianwilkerson@google.com, paulberry@google.com Bug: #29134 Change-Id: Ide76d50af921b04ce8cd6b96a0ee43f2a7734911 Reviewed-on: https://dart-review.googlesource.com/c/83321 Reviewed-by: Paul Berry <paulberry@google.com> Reviewed-by: Brian Wilkerson <brianwilkerson@google.com> Commit-Queue: Konstantin Shcheglov <scheglov@google.com>
Tentatively close. |
The buildbot has flakes of the following form (from this build):
It is not possible for me to reproduce this locally. Running the regeneration command is a NOP on my machine.
I will disable/skip this test for now.
@bwilkerson Would you mind taking a look?
The text was updated successfully, but these errors were encountered: