-
Notifications
You must be signed in to change notification settings - Fork 12.7k
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
ClangdTests.exe/TUSchedulerTests.ManyUpdates flaky on windows #50117
Comments
(#48455 is about a hang in this test suite -- looks like this code has a concurrency bug somewhere) |
This is happening a lot right now: http://45.33.8.238/win/80342/step_9.txt 5 failures in the last 1.5 days. |
@ilya-biryukov added this test over 5 years ago in https://reviews.llvm.org/D42174. |
See also clangd/clangd#1712 |
Hi all, sorry for missing those. Hi @nico, I was checking the failures in the past week, and they don't seem to be from clangd. Is this still relevant for the build bot you're running? |
closing as this doesn't seem to be showing up anymore on the relevant build bots at least, and despite the original bug being about a correctness issue, the recent failures are all timeouts. |
Extended Description
https://lab.llvm.org/buildbot/#/builders/123/builds/4487/steps/12/logs/stdio :
Same on https://lab.llvm.org/buildbot/#/builders/123/builds/4485/steps/12/logs/stdio
Same on https://lab.llvm.org/buildbot/#/builders/123/builds/4481/steps/12/logs/stdio
Same on https://lab.llvm.org/buildbot/#/builders/123/builds/4564/steps/12/logs/stdio
From a random sample, it looks like the majority of failures on https://lab.llvm.org/buildbot/#/builders/123 is due to this.
The text was updated successfully, but these errors were encountered: