-
Notifications
You must be signed in to change notification settings - Fork 13.4k
Improve rustdoc-gui CI #91181
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Improve rustdoc-gui CI #91181
Conversation
e7d54f4
to
94575e1
Compare
☔ The latest upstream changes (presumably #91203) made this pull request unmergeable. Please resolve the merge conflicts. |
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.
Thanks for the fix, this is great! r=me after rebase and tests passing.
94575e1
to
e340478
Compare
@bors: r=jsha |
📌 Commit e340478 has been approved by |
…ci, r=jsha Improve rustdoc-gui CI As commented [here](rust-lang#91179 (comment)): When the text isn't displayed, the color returned by puppeteer is always `rgba(0,0,0,0)`, which is definitely not the right value. To prevent this error from happening again, `browser-ui-test` will now fail if a CSS color check is run when the text isn't displayed. Either this PR or rust-lang#91179 is merged first, they'll conflict because I made changes to the same test file. cc `@jyn514` r? `@jsha`
…ci, r=jsha Improve rustdoc-gui CI As commented [here](rust-lang#91179 (comment)): When the text isn't displayed, the color returned by puppeteer is always `rgba(0,0,0,0)`, which is definitely not the right value. To prevent this error from happening again, `browser-ui-test` will now fail if a CSS color check is run when the text isn't displayed. Either this PR or rust-lang#91179 is merged first, they'll conflict because I made changes to the same test file. cc ``@jyn514`` r? ``@jsha``
…ci, r=jsha Improve rustdoc-gui CI As commented [here](rust-lang#91179 (comment)): When the text isn't displayed, the color returned by puppeteer is always `rgba(0,0,0,0)`, which is definitely not the right value. To prevent this error from happening again, `browser-ui-test` will now fail if a CSS color check is run when the text isn't displayed. Either this PR or rust-lang#91179 is merged first, they'll conflict because I made changes to the same test file. cc ```@jyn514``` r? ```@jsha```
☀️ Test successful - checks-actions |
Finished benchmarking commit (a7836bf): comparison url. Summary: This benchmark run did not return any relevant changes. If you disagree with this performance assessment, please file an issue in rust-lang/rustc-perf. @rustbot label: -perf-regression |
As commented here:
When the text isn't displayed, the color returned by puppeteer is always
rgba(0,0,0,0)
, which is definitely not the right value. To prevent this error from happening again,browser-ui-test
will now fail if a CSS color check is run when the text isn't displayed.Either this PR or #91179 is merged first, they'll conflict because I made changes to the same test file.
cc @jyn514
r? @jsha