-
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
Running compile-fail tests after changing code results in "found crate std
compiled by an incompatible version of rustc"
#39751
Comments
I've had the same issues a few times myself. |
I believe this is a dupe of #39396, so closing in favor of that. |
@shepmaster oh this may actually be a preexisting bug in the build system. If you make a commit while you're working then the artifacts can get mixed up because the version has the git rev in it. |
I forget if I made a commit or not. It's possible I might have, under the impression that changing the |
Yeah changing the head commit is something we don't check for right now but probably should! It looks like though that this is separate from #39396 so I'm gonna reopen. |
Is there a workaround for this? I've just done |
That should just recompile compiletest |
|
|
This should be fixed by #43421, which will recompile the necessary crates based on their environment dependencies. |
I was trying to follow a TDD-like process:
python ../x.py test ../src/test/compile-fail/
- note that only my test is failing, as expectedsrc/librustc_typeck/check/mod.rs
to address the failurepython ../x.py test ../src/test/compile-fail/
- all tests failThe error from one of the tests:
The build script says that the build is complete:
This is using 2425b22.
The text was updated successfully, but these errors were encountered: