-
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
Move rustdoc run-make-fulldeps tests to run-make #83775
Conversation
@bors r+ |
📌 Commit b46f615 has been approved by |
Move rustdoc run-make-fulldeps tests to run-make This cuts the time to run the tests in half, because they don't require building a stage 2 compiler. They were all added to fulldeps before rust-lang#82802 because rustdoc wasn't available in run-make tests. This doesn't change coverage tests, which will be changed soon in a separate PR (rust-lang#83755 (comment)). This also changes some of the `-include` directives, see rust-lang#83773 for what's going on there. r? `@petrochenkov`
@petrochenkov do you understand this test failure?
My only thought is that different args are being passed depending on the stage? I looked for |
Looks like we are building for x86_64 Linux (that's where It may be possible that the |
☔ The latest upstream changes (presumably #83880) made this pull request unmergeable. Please resolve the merge conflicts. |
This cuts the time to run the tests in half, because they don't require building a stage 2 compiler. This doesn't change coverage tests, which will be changed soon in a separate PR.
I'm still not sure exactly what's going on, but it's related to cross-compiling - I can reproduce locally with
Maybe passing -Clinker=arm-gcc is incorrect here? I don't know whether run-make tests are supposed to depend on the target or not. I think stage2 is unrelated - I used I meant to see what the command was for run-make-fulldeps (in particular, to see whether it passed -Clinker=arm-gcc or not), but my computer crashed and I didn't want to lose the part of the comment I'd written up. |
If there's a deeper problem with run-make, should we open an issue to track that and close this for the time being? |
@bstrie I don't understand what's going on well enough to know if it's an issue with run-make or not, and if so, what it is. |
☔ The latest upstream changes (presumably #85711) made this pull request unmergeable. Please resolve the merge conflicts. |
ping from triage: |
I will not have time to work on this in the foreseeable future. |
…ulacrum Move almost all run-make-fulldeps tests to run-make They pass fine, and this avoids having to build the compiler twice. There are few enough tests left that I think it should be possible to get rid of this test suite altogether, but I expect this PR to fail at least a few times in bors and want to get it merged before tackling further changes. cc rust-lang#83775 Fixes rust-lang#66085. Fixes rust-lang#83773.
Move almost all run-make-fulldeps tests to run-make They pass fine, and this avoids having to build the compiler twice. There are few enough tests left that I think it should be possible to get rid of this test suite altogether, but I expect this PR to fail at least a few times in bors and want to get it merged before tackling further changes. cc rust-lang/rust#83775 Fixes rust-lang/rust#66085. Fixes rust-lang/rust#83773.
This cuts the time to run the tests in half, because they don't require
building a stage 2 compiler. They were all added to fulldeps before #82802 because rustdoc wasn't available in run-make tests.
This doesn't change coverage tests, which will be changed soon in a
separate PR (#83755 (comment)).
This also changes some of the
-include
directives, see #83773 for what's going on there.r? @petrochenkov