-
Notifications
You must be signed in to change notification settings - Fork 13.2k
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
llvm rebuild failure on windows buildbot #11042
Comments
Sadly this is just a known issue. Windows rebuilds of LLVM will always fail on the first rebuild, and you must re-invoke make to get llvm to build. I've tried to look into this before, but I've never come up with much. |
I now think it only occurs on buildbots. It's really strange that From previous log, auto-win-32-opt/builds/2830 failed to remove/create This and this discuss |
I have to admit that I got this error on my machine (Windows 8.1pre) some days ago. :-( |
Looks like this got fixed upstream. The LLVM upgrade yesterday didn't bounce like this. |
[`unused_async`]: don't lint if function is part of a trait Fixes rust-lang#10459. We shouldn't lint if the function is part of a trait, because the user won't be able to easily remove the `async`, as this will then not match with the function signature in the trait definition changelog: [`unused_async`]: don't lint if function is part of a trait
bors always get some build failure (so requires several retries) on windows during llvm rebuild. Recent failure log here. It ends with:
I'm not sure if it occurs only on buildbot or on any windows machine; it's worth to investigate.
The text was updated successfully, but these errors were encountered: