-
Notifications
You must be signed in to change notification settings - Fork 12.8k
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
x.py
sometimes causes spurious rebuilds of rustc
#80849
Comments
Can you try running with CARGO_LOG=cargo::core::compiler::fingerprint=info and provide a build log when you see a spurious rebuild? |
Got one [ended after seeing it was building Log
Also encountered an ICE that I'll file a bug report for (#80852). |
cc @rust-lang/cargo, any idea on what could be causing the nothing obvious fingerprint error here? Or how to debug it? |
It looks like this has to do with:
is this a case where a |
Hm, yes, we're definitely tracking sysroot files, but they shouldn't be missing - @PatchMixolydic can you check whether those files are actually present? Do you perhaps have something like x.py check running from your editor in the background? |
That file does seem to exist. I am running |
I think this is a duplicate of #76661. |
…Simulacrum Lock bootstrap (x.py) build directory Closes rust-lang#76661, closes rust-lang#80849, `x.py` creates a lock file at `project_root/lock.db` r? `@jyn514` , because he was one that told me about this~
…Simulacrum Lock bootstrap (x.py) build directory Closes rust-lang#76661, closes rust-lang#80849, `x.py` creates a lock file at `project_root/lock.db` r? ``@jyn514`` , because he was one that told me about this~
I tried this:
src/test/ui/fn/issue-80844-no-gate.rs
$ ./x.py test src/test/ui/fn
I expected to see this happen: the
ui/fn
test suite is run, possibly building the testsuite binary using the existing stage 1rustc
.Instead, this happened: the stage 1
rustc
is rebuilt before running the test suite.This seems to happen randomly; I had rerun the test suite quite a few times using the same command with no issues. This is rather inconvenient since even with 16 logical cores, building
rustc
takes several minutes and grinds my machine to a halt.This doesn't just seem to happen when running the test suite, but I'm less confident about saying that rebuilds after modifying rustc's codebase are spurious.
@rustbot modify labels +A-contributor-roadblock +A-rustbuild
The text was updated successfully, but these errors were encountered: