-
-
Notifications
You must be signed in to change notification settings - Fork 14.4k
Try to reduce rustdoc GUI tests flakyness #151692
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
Conversation
There was a problem hiding this 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
|
@bors r+ rollup |
…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
|
Scheduling: If the rollup fails legitimately, fall back to this PR. @bors p=4 |
|
⌛ Testing commit 21ebd03 with merge f3ada21... Workflow: https://github.com/rust-lang/rust/actions/runs/21386838846 |
|
@bors yield (to enclosing rollup) |
|
Auto build cancelled. Cancelled workflows: The next pull request likely to be tested is #151727. |
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)
|
The rollup still failed with this CI error: #151743 |
|
So I guess it didn't fix it. :3 |
|
This one as well |
|
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). |
|
That could also be in PR ci tho, then it's not in the way of other work |
|
No: that's the whole issue with flakyness: doesn't happen all |
|
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. |
Should help with #93784.
I replaced a use of
puppeteer.waitfunction with a loop instead (like the rest ofbrowser-ui-test).r? @jieyouxu