-
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
Print a summary of which test suite failed #78705
Print a summary of which test suite failed #78705
Conversation
@Mark-Simulacrum: no appropriate reviewer found, use r? to override |
Looks great! Line 1299 in a6403b0
Do you want to keep these two in sync in terms of output? One uses |
Especially on CI, where cross-compiling is common and single builder may end up with multiple hosts and multiple targets, it can be annoying to scroll back to the nearest start of test marker. This prints out a summary of the test suite being run directly in compiletest.
370e9ab
to
f289a87
Compare
IMO the HOST -> TARGET terminology is a bit confusing and likely not immediately obvious; I don't personally care to change the (many) locations in bootstrap right now, but I also think consistency in this case is not too important. I think this could be in bootstrap but -- as you noted on the issue -- it'd be annoying to pipe the relevant data in, and here we immediately have it available. |
Will the suite and mode ever be different? r=me if so, but otherwise I don't think we need to print both. |
I don't have the time to do a detailed investigation, but I suspect the answer is yes (or, at least, that this is plausible). The two are tracked and passed as separate things in bootstrap as well. |
Ok, they can be different:
@bors r+ |
📌 Commit f289a87 has been approved by |
💡 This pull request was already approved, no need to approve it again.
|
📌 Commit f289a87 has been approved by |
Rollup of 15 pull requests Successful merges: - rust-lang#74979 (`#![deny(unsafe_op_in_unsafe_fn)]` in sys/hermit) - rust-lang#78006 (Use Intra-doc links for std::io::buffered) - rust-lang#78167 (Fix unreachable sub-branch detection in or-patterns) - rust-lang#78514 (Allow using 1/2/3/4 for `x.py setup` options) - rust-lang#78538 (BTreeMap: document a curious assumption in test cases) - rust-lang#78559 (Add LLVM upgrades from 7 to 10 to RELEASES.md) - rust-lang#78666 (Fix shellcheck error) - rust-lang#78705 (Print a summary of which test suite failed) - rust-lang#78726 (Add link to rust website) - rust-lang#78730 (Expand explanation of reverse_bits) - rust-lang#78760 (`deny(invalid_codeblock_attributes)` for rustc_error_codes) - rust-lang#78771 (inliner: Copy unevaluated constants only after successful inlining) - rust-lang#78794 (rustc_expand: use collect_bang helper instead of manual reimplementation) - rust-lang#78795 (The renumber pass is long gone) - rust-lang#78798 (Fixing Spelling Typos) Failed merges: r? `@ghost` `@rustbot` modify labels: rollup
Especially on CI, where cross-compiling is common and single builder may end up
with multiple hosts and multiple targets, it can be annoying to scroll back to
the nearest start of test marker. This prints out a summary of the test suite
being run directly in compiletest.
For example, on a mir-opt failure, this would show something like this:
Fixes #78517