-
Notifications
You must be signed in to change notification settings - Fork 12.8k
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
new tool rustdoc-gui-test
#111348
new tool rustdoc-gui-test
#111348
Conversation
Failed to set assignee to
|
(rustbot has picked a reviewer for you, use r? to override) |
This comment has been minimized.
This comment has been minimized.
84e2def
to
380b7d7
Compare
How does this change looks like ? Is it overkill to use cc @jyn514 |
RUSTDOCFLAGS
flags in bootstraprustdoc-gui
b8431c2
to
ccfb1e8
Compare
rustdoc-gui
rustdoc-gui
How big is the function you're using? If it's not giant, I'd rather move just that function to |
Moving is even more complex because it requires a lot of functions and types to move. Alternative way to adding |
I think the right solution is to move rustdoc-gui to src/tools/compiletest so that all flags can be supported. |
They are quite different things IMO. -- If pulling compiletest from https://github.com/Manishearth/compiletest-rs is the problem, maybe we can use compiletest locally from |
A separate crate like compiletest (e.g., src/tools/rustdoc-gui) would avoid everyone building Rust needing to compile the extra dependencies, if you don't want to build it into compiletest proper. |
rustdoc-gui
rustdoc-gui-tests
rustdoc-gui-tests
rustdoc-gui-test
@rustbot blocked |
Signed-off-by: ozkanonur <[email protected]>
@bors r=albertlarsan68,oli-obk |
📌 Commit 0fb171795ce80fae65d381521d5bafcc0937affa has been approved by It is now in the queue for this repository. |
0fb1717
to
c7cec29
Compare
@bors r=albertlarsan68,oli-obk |
…-flags, r=albertlarsan68,oli-obk new tool `rustdoc-gui-test` Implements new tool `rustdoc-gui-test` that allows using compiletest headers for `rustdoc-gui` tests.
☀️ Test successful - checks-actions |
Finished benchmarking commit (dbfc95f): comparison URL. Overall result: no relevant changes - no action needed@rustbot label: -perf-regression Instruction countThis benchmark run did not return any relevant results for this metric. Max RSS (memory usage)ResultsThis is a less reliable metric that may be of interest but was not used to determine the overall result at the top of this comment.
CyclesThis benchmark run did not return any relevant results for this metric. Binary sizeThis benchmark run did not return any relevant results for this metric. Bootstrap: 645.695s -> 643.935s (-0.27%) |
@@ -8,13 +8,13 @@ set-window-size: (600, 800) | |||
assert-property: ("html", {"scrollTop": "0"}) | |||
|
|||
click: '//a[text() = "barbar"]' | |||
assert-property: ("html", {"scrollTop": "125"}) | |||
assert-property: ("html", {"scrollTop": "149"}) |
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 did these values change? Unless you changed the default size of the page, they should not have been updated.
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.
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.
I see, thanks! But why generating the links to def all the time then? Was there an issue to generate it only for one crate? It's a nightly-only option, so it should not be included all the time because it prevents us to test the almost 100% use-case, which is problematic imo.
Would have been nice if the rustdoc team was contacted for the changes in the rustdoc GUI test. I'm very nervous about this change as I don't understand why it's needed. |
|
You are right, we forgot doing that, sorry about that. The main reason for having this tool was to prevent the need for manually inserting test flags in bootstrap side. If we were to directly use compiletest in bootstrap, it would have made the bootstrapping process longer. |
I'm fine with the tool (and nice job!), just would have preferred to be pinged for the GUI test change to at least be aware of it. |
absoluletely true, again sorry for missing that |
Implements new tool
rustdoc-gui-test
that allows using compiletest headers forrustdoc-gui
tests.