-
Notifications
You must be signed in to change notification settings - Fork 13.4k
thread 'rustc' panicked at compiler/rustc_resolve/src/macros.rs:749:2 #142009
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
Comments
how odd. |
@GlenDC Does this repro if you change the runner to use nightly? |
Not sure, it's not even that consistent, it only happened once that I know so far, for a PR of a contributor. But a retry of the failed job made it succeed immediately, so it might be a hard one to track down. |
oh. incr comp...? |
Yes that must be it. But it's also the first time that I see this happening, despite 1.87 already out for a while, so must be an edge case |
This looks to be in a release build where incremental compilation is disabled. |
Looking at the difference in the CI logs between the failed and the successful build, it seems that it failed while uncompressing the cache (the cache is as far as I can tell the exact same in both builds):
Since the job continued after this, perhaps |
wild. |
And we're not in charge of that gtar invocation so we can't error on seeing that stdio, right? |
No, this is from GitHub's |
If |
....wild. |
Seen in: https://github.com/plabayo/rama/actions/runs/15433552048/job/43435739684
And only there. None of our other CI targets trigger it and locally (despite being on macOS as well)
we do not see it either.
Meta
rustc --version --verbose
:Error output
Backtrace
The text was updated successfully, but these errors were encountered: