-
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
edition suggestion UI tests fail when CARGO is set #118058
Comments
hm, this might be entangled with the cursed way i set up https://github.com/gankra/cargo-mommy with my |
hm, even |
So, rustc checks whether |
actually it probably is related to my cargo-mommy shenanigans, I set |
while the compiletest diff tried to tell me that its not set while it should be, the "unexpected errors" bit tells me that the env var is set while it shouldn't be. |
I tried running tests in a fresh checkout free of any shenanigans and that worked fine, so this is a me issue. and no, what seems to be happening is that the var ISN'T set for me, I manually checked the stderr dump from compiletest and it suggests |
In both my not working run and the working run, |
and in both runs, |
Okay, I resolved most of my confusion, leaving sane behavior that can be debugged:
Now I'm left with the sane behavior of |
Or rather, there is nothing to debug anymore. |
Rollup merge of rust-lang#118059 - Nilstrieb:unset-cargo, r=dtolnay Explicitly unset $CARGO for compiletest Some UI tests trigger behavior in rustc where it reads $CARGO and changes behavior if it exists. To make the tests work that rely on it not being set, make sure it is not set. By default, this is not set, but people may do weird hacks that cause it to be set. closes rust-lang#118058
The text was updated successfully, but these errors were encountered: