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 on Windows buildbot #5133
Comments
Issue #2708 has been merged into this issue. |
This is back again, the last investigation did not seem to indicate that the bot was under heavy load and the current occurrence does not indicate that the run was slower than the previous run (on the contrary actually, it is slightly faster) VM team: how do we implement sleep? do we use windows timer granularity (which is pretty bad, something like 15 ms as far as I remember) cc @iposva-google. |
Issue #9199 has been merged into this issue. |
This problem has suddenly started making it very difficult to get a build out. Can someone on the VM team please take a look at this, or disable the teset? Removed Priority-Medium label. |
Marked flaky in r20266, so this won't block the builds any longer. Removed Priority-Critical label. |
Issue #10409 has been merged into this issue. |
Added this to the Later milestone. |
The issue in comment #3 and comment #4 is unrelated to this original bug report. I will unmerge the issues. |
Removed this from the Later milestone. |
Removed Oldschool-Milestone-Later label. |
Stale. |
I've skipped the test. At least the following alternatives are available:
Marking it as flaky in a status file serves no purpose. |
There are no current VM people cc'ed on this |
Thank you! |
The tests vm/cc/Sleep and vm/cc/Monitor are flaky on the Windows debug buildbot. The frequency of flakiness increased so we should investigate that buildbot setup and load.
The text was updated successfully, but these errors were encountered: