-
Notifications
You must be signed in to change notification settings - Fork 13.1k
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
run-make-fulldeps/linker-output-non-utf8 failure #63520
Comments
Compiler team pre-triage: marking as P-medium, this is probably something wacky in my local setup. We'll see if others complain about it. |
I have also seen this in Fedora and RHEL builds, but I didn't worry enough to chase it down yet. This error is actually from rust/src/librustc_driver/lib.rs Lines 1189 to 1194 in 1cdcea9
Arguments 5 and 6 from the
That line is deliberately added in the rust/src/test/run-make-fulldeps/linker-output-non-utf8/Makefile Lines 17 to 23 in 1cdcea9
I have no idea why this isn't an issue in CI though... |
Oh, I think I do know why. That bash:
dash:
So I think this test hasn't really been working as desired on |
Note, the |
Any idea what to do with this test? |
We can probably just remove that test, it doesn't seem worth the pain of having it if it's causing people problems. It sounds like we don't have a test case that would work universally even on *nix platforms, right? Or that's my interpretation of #63520 (comment) at least. It's also pretty unclear to me that ICE-ing on non-utf8 output from linkers is something we need to test for. That sounds both incredibly uncommon, and also pretty easily fixable if we need to. One thought for testing this is to override the linker rustc uses with a shell script or even a rust program that runs the linker internally but just does something like |
This test continues to be super annoying. I'm happy to just remove it, per @Mark-Simulacrum's suggestion. |
Okay I've filed #65321 to remove the test -- seems like everyone is in agreement it does not pull its weight. |
…f8-test, r=nikomatsakis Remove painful test that is not pulling its weight Research suggests that we are not properly testing this case anyway, and even if we were, it is unlikely that we will regress here -- or, perhaps more accurately, if we do, I am uncertain that we care too much. It definitely seems like an edge case, and one that is particularly unlikely to occur as time goes on. Fixes rust-lang#63520
when running
x.py test
locally I get errors in the testrun-make-fulldeps/linker-output-non-utf8
:The most notable part being this:
perhaps related to the linker on my system?
The text was updated successfully, but these errors were encountered: