Skip to content

Conversation

@GuillaumeGomez
Copy link
Member

Should help with #93784.

I replaced a use of puppeteer.wait function with a loop instead (like the rest of browser-ui-test).

r? @jieyouxu

@rustbot rustbot added S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. T-rustdoc Relevant to the rustdoc team, which will review and decide on the PR/issue. T-rustdoc-frontend Relevant to the rustdoc-frontend team, which will review and decide on the web UI/UX output. labels Jan 26, 2026
Copy link
Member

@jieyouxu jieyouxu left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Let's give this a shot, thanks

View changes since this review

@jieyouxu
Copy link
Member

@bors r+ rollup

@rust-bors
Copy link
Contributor

rust-bors bot commented Jan 27, 2026

📌 Commit 21ebd03 has been approved by jieyouxu

It is now in the queue for this repository.

@rust-bors rust-bors bot added S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion. and removed S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. labels Jan 27, 2026
Zalathar added a commit to Zalathar/rust that referenced this pull request Jan 27, 2026
…youxu

Try to reduce rustdoc GUI tests flakyness

Should help with rust-lang#93784.

I replaced a use of `puppeteer.wait` function with a loop instead (like the rest of `browser-ui-test`).

r? @jieyouxu
@Zalathar
Copy link
Member

Scheduling: If the rollup fails legitimately, fall back to this PR.

@bors p=4

rust-bors bot pushed a commit that referenced this pull request Jan 27, 2026
Rollup of 4 pull requests

Successful merges:

 - #147436 (slice/ascii: Optimize `eq_ignore_ascii_case` with auto-vectorization)
 - #151390 (Reintroduce `QueryStackFrame` split.)
 - #151534 (target: fix destabilising target-spec-json)
 - #151692 (Try to reduce rustdoc GUI tests flakyness)
@rust-bors
Copy link
Contributor

rust-bors bot commented Jan 27, 2026

⌛ Testing commit 21ebd03 with merge f3ada21...

Workflow: https://github.com/rust-lang/rust/actions/runs/21386838846

rust-bors bot pushed a commit that referenced this pull request Jan 27, 2026
Try to reduce rustdoc GUI tests flakyness

Should help with #93784.

I replaced a use of `puppeteer.wait` function with a loop instead (like the rest of `browser-ui-test`).

r? @jieyouxu
@Zalathar
Copy link
Member

@bors yield (to enclosing rollup)

@rust-bors
Copy link
Contributor

rust-bors bot commented Jan 27, 2026

Auto build cancelled. Cancelled workflows:

The next pull request likely to be tested is #151727.

rust-bors bot pushed a commit that referenced this pull request Jan 27, 2026
Rollup of 5 pull requests

Successful merges:

 - #151692 (Try to reduce rustdoc GUI tests flakyness)
 - #147436 (slice/ascii: Optimize `eq_ignore_ascii_case` with auto-vectorization)
 - #151390 (Reintroduce `QueryStackFrame` split.)
 - #151097 (Use an associated type default for `Key::Cache`.)
 - #151702 (Omit standard copyright notice)
@rust-bors rust-bors bot merged commit 8ae4aca into rust-lang:main Jan 27, 2026
11 of 12 checks passed
@rustbot rustbot added this to the 1.95.0 milestone Jan 27, 2026
rust-timer added a commit that referenced this pull request Jan 27, 2026
Rollup merge of #151692 - GuillaumeGomez:reduce-flaky, r=jieyouxu

Try to reduce rustdoc GUI tests flakyness

Should help with #93784.

I replaced a use of `puppeteer.wait` function with a loop instead (like the rest of `browser-ui-test`).

r? @jieyouxu
@GuillaumeGomez GuillaumeGomez deleted the reduce-flaky branch January 27, 2026 13:30
@JonathanBrouwer
Copy link
Contributor

The rollup still failed with this CI error: #151743

@GuillaumeGomez
Copy link
Member Author

So I guess it didn't fix it. :3

@JonathanBrouwer
Copy link
Contributor

This one as well
#151704 (comment)
Since it seems to be always the same test, is it reasonable to disable this test for now until we have a proper fix?
How critical is the test?

@GuillaumeGomez
Copy link
Member Author

I'd rather not. I have some ideas. The only way to know a flaky is fixed (or not), is sadly to have a lot of potential CI failures).

@JonathanBrouwer
Copy link
Contributor

That could also be in PR ci tho, then it's not in the way of other work

@GuillaumeGomez
Copy link
Member Author

No: that's the whole issue with flakyness: doesn't happen all
3the tim8e9999999999999999

@GuillaumeGomez
Copy link
Member Author

Cat finished the comment in my stead. So I was trying to say: flaky tests don't fail all the time, proof with this PR which got merged although it didn't fix flakyness issue. So to ensure that it actually fixes it, I think we'll need to keep it enabled. Anyway, I have a few ideas I wanna investigate.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion. T-rustdoc Relevant to the rustdoc team, which will review and decide on the PR/issue. T-rustdoc-frontend Relevant to the rustdoc-frontend team, which will review and decide on the web UI/UX output.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants