-
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
Unignore tests in stage1 #25338
Unignore tests in stage1 #25338
Conversation
(rust_highfive has picked a reviewer for you, use r? to override) |
db662d2
to
c032e81
Compare
Just to confirm, have you run all these tests in stage1? Plugins fundamentally don't work in stage1, so many of these I believe are intentional. |
I haven't, but I'll do that now! |
Hm. |
Ah right, it is possible for these tests to work at stage1 (if codegen is similar enough in stage0 and stage1), but it's not guaranteed. For example if codegen changes after stage0 then plugins will be broken. |
So: wat do? |
I think that this should back out the removal of |
I think it's probably OK to unignore compilefail-fulldeps; do you agree? |
85982d2
to
80266b7
Compare
I think it kinda depends on the test. Anything which expects |
@alexcrichton is there a change I can make locally to induce the condition that would break these tests in stage1? feels a bit like a guessing game otherwise. |
I think if you change the symbol hashing function it'll cause the symbols to be totally different at stage1 than they were at stage0, so you can try just adding |
We don't have any pending snapshot-requiring changes. Tests which continue to be ignored are those that are broken by codegen changes.
80266b7
to
f548a05
Compare
Your suggestion worked! I tested these locally and they passed (with the hashing change) so this should be good to merge. Thanks for your help @alexcrichton. |
@bors: r+ f548a05 Nice! Thanks! |
@bors: rollup |
⌛ Testing commit f548a05 with merge b1bd3a3... |
We don't have any pending snapshot-requiring changes.
Works toward #3965.