-
Notifications
You must be signed in to change notification settings - Fork 13.9k
[rustdoc] Correctly handle should_panic doctest attribute and fix --no-run test flag on the 2024 edition
#147674
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
base: master
Are you sure you want to change the base?
Conversation
|
|
|
Let's see if it works like that, otherwise I'll add some |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
439161b to
4cc12dc
Compare
This comment has been minimized.
This comment has been minimized.
4cc12dc to
a7d6109
Compare
This comment has been minimized.
This comment has been minimized.
a7d6109 to
a47e09f
Compare
This comment has been minimized.
This comment has been minimized.
|
Ah right, forgot to fix std doc examples. |
|
Checking all previously failing CIs. @bors try jobs=armhf-gnu,test-various,x86_64-gnu-aux |
This comment has been minimized.
This comment has been minimized.
[rustdoc] Correctly handle `should_panic` doctest attribute and fix `--no-run` test flag on the 2024 edition try-job: armhf-gnu try-job: test-various try-job: x86_64-gnu-aux
|
💔 Test for 0c093af failed: CI. Failed jobs:
|
This comment has been minimized.
This comment has been minimized.
|
So the error comes from the fact that Let's try again. @bors try jobs=armhf-gnu,test-various,x86_64-gnu-aux |
This comment has been minimized.
This comment has been minimized.
[rustdoc] Correctly handle `should_panic` doctest attribute and fix `--no-run` test flag on the 2024 edition try-job: armhf-gnu try-job: test-various try-job: x86_64-gnu-aux
|
💔 Test for 7103c01 failed: CI. Failed jobs:
|
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
8ab42d9 to
641f107
Compare
|
💔 Test for 5ab1076 failed: CI. Failed jobs:
|
bd3fe05 to
11458ed
Compare
|
@bors try jobs=test-various |
This comment has been minimized.
This comment has been minimized.
[rustdoc] Correctly handle `should_panic` doctest attribute and fix `--no-run` test flag on the 2024 edition try-job: test-various
This comment has been minimized.
This comment has been minimized.
|
Just in case... @bors try jobs=test-various |
This comment has been minimized.
This comment has been minimized.
[rustdoc] Correctly handle `should_panic` doctest attribute and fix `--no-run` test flag on the 2024 edition try-job: test-various
This comment has been minimized.
This comment has been minimized.
|
@Kobzol: Do you know why we run stage1 |
|
Because it's in our CI config 😆 Does it cause some issues? |
|
I don't think so, I was just surprised to see some tests running with stage 1 and wondered if I broke something somehow. ^^' |
|
☔ The latest upstream changes (presumably #148280) made this pull request unmergeable. Please resolve the merge conflicts. |
…test` API directly
5e2a4aa to
47a06b7
Compare
|
This PR was rebased onto a different master commit. Here's a range-diff highlighting what actually changed. Rebasing is a normal part of keeping PRs up to date, so no action is needed—this note is just to help reviewers. |
|
The job Click to see the possible cause of the failure (guessed by this bot)For more information how to resolve CI failures of this job, visit this link. |
Fixes #143009.
Fixes #143858.
Supersedes #143900.
For
--no-run, we forgot to check the "global" options in the 2024 edition, fixed in the first commit.For should_panic fix, the exit code check has been fixed.
r? @fmease