-
-
Notifications
You must be signed in to change notification settings - Fork 14.3k
Use functions more in rustdoc GUI tests #150762
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
This comment has been minimized.
This comment has been minimized.
82c3bf1 to
0433639
Compare
|
And fixed |
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.
Everything looks good, except for the check-colors test for most of the themes being removed with no explanation.
| call-function: ("check-colors", { | ||
| "theme": "dark", | ||
| "doc_code_color": "#ddd", | ||
| "doc_inline_code_color": "#ddd", | ||
| }) | ||
| call-function: ("check-colors", { | ||
| "theme": "light", | ||
| "doc_code_color": "black", | ||
| "doc_inline_code_color": "black", | ||
| }) |
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.
Why was this removed??
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.
Woops. When I was debugging an issue in browser-ui-test I removed the extra lines to get less noise. Good catch!
0433639 to
945e7c7
Compare
|
Put back wrongly removed code. |
|
Thanks! @bors r+ |
Use functions more in rustdoc GUI tests Now that conditions are supported in `browser-ui-test`, we can start simplify some parts of the tests. This is a first cleanup, but I guess a lot more could be simplified. For follow-ups I guess. :) I made some improvements in backtrace display in `browser-ui-test`, hence the version update once more. r? @lolbinarycat
Use functions more in rustdoc GUI tests Now that conditions are supported in `browser-ui-test`, we can start simplify some parts of the tests. This is a first cleanup, but I guess a lot more could be simplified. For follow-ups I guess. :) I made some improvements in backtrace display in `browser-ui-test`, hence the version update once more. r? @lolbinarycat
Use functions more in rustdoc GUI tests Now that conditions are supported in `browser-ui-test`, we can start simplify some parts of the tests. This is a first cleanup, but I guess a lot more could be simplified. For follow-ups I guess. :) I made some improvements in backtrace display in `browser-ui-test`, hence the version update once more. r? @lolbinarycat
|
@bors rollup |
Rollup of 11 pull requests Successful merges: - #150272 (docs(core): update `find()` and `rfind()` examples) - #150385 (fix `Expr::can_have_side_effects` for `[x; N]` style array literal and binary expressions) - #150561 (Finish transition from `semitransparent` to `semiopaque` for `rustc_macro_transparency`) - #150574 (Clarify `MoveData::init_loc_map`.) - #150762 (Use functions more in rustdoc GUI tests) - #150808 (rename the `derive_{eq, clone_copy}` features to `*_internals`) - #150816 (Fix trait method anchor disappearing before user can click on it) - #150821 (tests/ui/borrowck/issue-92157.rs: Remove (bug not fixed)) - #150829 (make attrs actually use `Target::GenericParam`) - #150834 (Add tracking issue for `feature(multiple_supertrait_upcastable)`) - #150864 (The aarch64-unknown-none target requires NEON, so the docs were wrong.) r? @ghost
Rollup merge of #150762 - cleanup-gui, r=lolbinarycat Use functions more in rustdoc GUI tests Now that conditions are supported in `browser-ui-test`, we can start simplify some parts of the tests. This is a first cleanup, but I guess a lot more could be simplified. For follow-ups I guess. :) I made some improvements in backtrace display in `browser-ui-test`, hence the version update once more. r? @lolbinarycat
Rollup of 11 pull requests Successful merges: - rust-lang/rust#150272 (docs(core): update `find()` and `rfind()` examples) - rust-lang/rust#150385 (fix `Expr::can_have_side_effects` for `[x; N]` style array literal and binary expressions) - rust-lang/rust#150561 (Finish transition from `semitransparent` to `semiopaque` for `rustc_macro_transparency`) - rust-lang/rust#150574 (Clarify `MoveData::init_loc_map`.) - rust-lang/rust#150762 (Use functions more in rustdoc GUI tests) - rust-lang/rust#150808 (rename the `derive_{eq, clone_copy}` features to `*_internals`) - rust-lang/rust#150816 (Fix trait method anchor disappearing before user can click on it) - rust-lang/rust#150821 (tests/ui/borrowck/issue-92157.rs: Remove (bug not fixed)) - rust-lang/rust#150829 (make attrs actually use `Target::GenericParam`) - rust-lang/rust#150834 (Add tracking issue for `feature(multiple_supertrait_upcastable)`) - rust-lang/rust#150864 (The aarch64-unknown-none target requires NEON, so the docs were wrong.) r? @ghost
Now that conditions are supported in
browser-ui-test, we can start simplify some parts of the tests. This is a first cleanup, but I guess a lot more could be simplified. For follow-ups I guess. :)I made some improvements in backtrace display in
browser-ui-test, hence the version update once more.r? @lolbinarycat