-
Notifications
You must be signed in to change notification settings - Fork 12.7k
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
Reduce rustdoc GUI tests flakyness #126436
Reduce rustdoc GUI tests flakyness #126436
Conversation
With this great documentation, the fix looks simple to review. If you don't absolutely need notriddle's r+, you can have my r+ once the |
This is very nice of you. 😉 Then let's go! @bors r=lqd rollup |
…akyness, r=lqd Reduce rustdoc GUI tests flakyness Fixes rust-lang#126430. r? `@notriddle`
…iaskrgr Rollup of 9 pull requests Successful merges: - rust-lang#121216 (Always emit `native-static-libs` note, even if it is empty) - rust-lang#123962 (change method resolution to constrain hidden types instead of rejecting method candidates) - rust-lang#126285 (`UniqueRc`: support allocators and `T: ?Sized`.) - rust-lang#126315 (Add pub struct with allow(dead_code) into worklist) - rust-lang#126320 (Avoid ICES after reporting errors on erroneous patterns) - rust-lang#126343 (Remove some msys2 utils) - rust-lang#126351 (std::unix::fs::link using direct linkat call for Solaris.) - rust-lang#126399 (extend the check for LLVM build) - rust-lang#126436 (Reduce rustdoc GUI tests flakyness) r? `@ghost` `@rustbot` modify labels: rollup
This comment has been minimized.
This comment has been minimized.
:/ |
That's interesting! @bors r- |
3de874a
to
d78746c
Compare
should go next whenever it clears CI |
r=me when |
This comment has been minimized.
This comment has been minimized.
@bors treeclosed=13 |
I don't understand why the code used in literally all GUI doctests is failing only in this one test, especially since we didn't update the test nor the rustdoc output in quite a long time. I added some debug information, let's see if it's helpful... |
Until I figure out what's wrong with this test, I opened #126445 to remove it so the rust's CI is unblocked. |
The job Click to see the possible cause of the failure (guessed by this bot)
|
Remove failing GUI test to stop blocking CI until it is fixed Until rust-lang#126436 is solved, let's unblock rust CI. r? `@lqd`
Remove failing GUI test to stop blocking CI until it is fixed Until rust-lang#126436 is solved, let's unblock rust CI. r? `@lqd`
@bors treeclosed- |
☔ The latest upstream changes (presumably #126445) made this pull request unmergeable. Please resolve the merge conflicts. |
no shit, really? |
The job Click to see the possible cause of the failure (guessed by this bot)
|
Yep, that was completely useless. All test commands are run as expected, but the rustdoc JS seems to not be run for some reason... I'll try to see if maybe something changed on the CI side. |
…=notriddle Update browser-ui-test version to `0.18.0` Should help with rust-lang#126436. r? `@notriddle`
…=notriddle Update browser-ui-test version to `0.18.0` Should help with rust-lang#126436. r? ``@notriddle``
…=notriddle Update browser-ui-test version to `0.18.0` Should help with rust-lang#126436. r? ```@notriddle```
…otriddle Update browser-ui-test version to `0.18.0` Should help with rust-lang#126436. r? `@notriddle`
Fixes #126430.
r? @notriddle