-
Notifications
You must be signed in to change notification settings - Fork 12.5k
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
Repeated spurious rustdoc test failure: rustdoc-gui/help-page #126430
Labels
A-ci
Area: Our Github Actions CI
A-spurious
Area: Spurious failures in builds (spuriously == for no apparent reason)
A-testsuite
Area: The testsuite used to check the correctness of rustc
C-bug
Category: This is a bug.
T-rustdoc
Relevant to the rustdoc team, which will review and decide on the PR/issue.
Comments
rustbot
added
the
needs-triage
This issue may need triage. Remove it if it has been sufficiently triaged.
label
Jun 13, 2024
This was referenced Jun 13, 2024
Noratrieb
added
A-testsuite
Area: The testsuite used to check the correctness of rustc
T-rustdoc
Relevant to the rustdoc team, which will review and decide on the PR/issue.
A-spurious
Area: Spurious failures in builds (spuriously == for no apparent reason)
C-bug
Category: This is a bug.
A-ci
Area: Our Github Actions CI
and removed
needs-triage
This issue may need triage. Remove it if it has been sufficiently triaged.
labels
Jun 13, 2024
Taking a look. |
matthiaskrgr
added a commit
to matthiaskrgr/rust
that referenced
this issue
Jun 13, 2024
…akyness, r=lqd Reduce rustdoc GUI tests flakyness Fixes rust-lang#126430. r? `@notriddle`
It was "fixed" in #127082 (still no idea why this test in particular is failing). |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
A-ci
Area: Our Github Actions CI
A-spurious
Area: Spurious failures in builds (spuriously == for no apparent reason)
A-testsuite
Area: The testsuite used to check the correctness of rustc
C-bug
Category: This is a bug.
T-rustdoc
Relevant to the rustdoc team, which will review and decide on the PR/issue.
I've seen this fail in two PRs today, e.g. here
Cc @rust-lang/rustdoc
The text was updated successfully, but these errors were encountered: