Uh oh!
There was an error while loading. Please reload this page.
Test rustdoc js - #47250
Conversation
rust-highfive
commented
Jan 7, 2018
Some changes occurred in HTML/CSS. |
rust-highfive
commented
Jan 7, 2018
(rust_highfive has picked a reviewer for you, use r? to override) |
GuillaumeGomez
commented
Jan 7, 2018
Ah apparently, @Mark-Simulacrum is the one! Could you give me a hand when you have time please? |
There was a problem hiding this comment.
- The
_probably needs to bebuilderfor line 457 to work. - This function needs to return
Self::Outputanyway, for the trait to match. SinceSelf::OutputisPathBuf, that's what this needs to return. However, all of the otherStepimpls in this file return(), so that's probably what theOutputneeds to be here as well.
There was a problem hiding this comment.
Certainly, I stopped trying to make it work and certainly forgot to commit the version which compiles. The problem is more global anyway. But thanks for taking a look in here. ;)
Mark-Simulacrum
left a comment
There was a problem hiding this comment.
Left some basic feedback. Let me know if you have any questions.
There was a problem hiding this comment.
You almost certainly want these arguments to be closer to the above. Something like RustdocJs, "rustdoc-js", "js-tests", Mode::Tool.
But frankly I'm not entirely certain what this tool is doing either way -- you'd probably actually not want it, or at least it seems like at the very least it shouldn't be generated by the macro. If this doesn't make sense, explaining why it's here would help.
There was a problem hiding this comment.
I just tried my best understanding what was going on in here. My goal is to test the search in rust documentation. So I need to run this tool once the documentation has been generated. To run it, I need nodejs and I don't really know how to pick up the currently installed one.
There was a problem hiding this comment.
This should be something more reasonable, like src/tests/rustdoc-js.
There was a problem hiding this comment.
The commands here likely want to use the configured node executable (builder.config.nodejs or something like that).
There was a problem hiding this comment.
This (probably) shouldn't be here, unless you want to branch on rustdoc-js as the mode below and call into RustdocJs... I would remove this, and add RustdocJs to the list of tests here
Lines 254 to 257 in ee220da
GuillaumeGomez
commented
Jan 8, 2018
@Mark-Simulacrum: Ok, moved a bit forward (still not compiling). Are you sure I need to put |
Mark-Simulacrum
commented
Jan 10, 2018
Sorry for the delay in getting back to you. Since the tool |
GuillaumeGomez
commented
Jan 10, 2018
It requires at least rustdoc compilation in order to have a doc built (I need generated docs). Therefore it requires rustc and everything coming beforehand. :) |
Mark-Simulacrum
commented
Jan 10, 2018
So if you need specific generated docs, you can call Does that help? |
7edd379 to
6952199CompareGuillaumeGomez
commented
Jan 12, 2018
Yes, thanks a lot! This is now ready on my side. |
Mark-Simulacrum
commented
Jan 13, 2018
Looks like we'll need to install nodejs for this to work. cc @alexcrichton -- are we okay with a default test requiring this (new) dependency? You can see examples of how we do it in the emscripten script: https://github.com/rust-lang/rust/blob/master/src/ci/docker/scripts/emscripten.sh#L50-L53. |
alexcrichton
commented
Jan 13, 2018
Could we perhaps not run these tests by default but run them on one builder or when node is already detected? I think it'd be best to not pick up a new dependency for all builds but just some (opt-in) builds. |
GuillaumeGomez
commented
Jan 13, 2018
Sure. Let's go for testing only when node is present. |
GuillaumeGomez
commented
Jan 13, 2018
Done! |
GuillaumeGomez
commented
Jan 15, 2018
I'll put the explanation in this comment, don't hesitate to copy/paste it anywhere you might want. This PR is pretty "simple" and "just" add tests for the rustdoc search. It was heavily required because of all the recent breaking changes that happened while I went through improvements in doc search (add search in/for generic search for example). |
Mark-Simulacrum
commented
Jan 15, 2018
r=me if you're ready and don't want docs team review; I have not looked over the tests themselves to verify that they make sense. It is also be worth checking that we have at least one builder on CI that would run these tests, and if not, probably adding nodejs to one of our test-running builders. My impression is that |
GuillaumeGomez
commented
Jan 15, 2018
The doc team already gave its go through @QuietMisdreavus so I suppose it's fine. For me it seems good enough for a first step. We can always add more later on. :) Thanks a lot for your help in here @Mark-Simulacrum! @bors: r=Mark-Simulcram |
bors
commented
Jan 15, 2018
📌 Commit 026c749 has been approved by |
Mark-Simulacrum
commented
Jan 15, 2018
@bors r- r+ |
bors
commented
Jan 15, 2018
💡 This pull request was already approved, no need to approve it again.
|
bors
commented
Jan 15, 2018
📌 Commit 026c749 has been approved by |
…ark-Simulacrum Test rustdoc js Add tests for the rustdoc search. It was heavily required because of all the recent breaking changes that happened while I went through improvements in doc search (add search in/for generic search for example).
GuillaumeGomez
commented
Jan 16, 2018
Apparently windows uses an old version: |
GuillaumeGomez
commented
Jan 16, 2018
@bors: r=Mark-Simulacrum |
bors
commented
Jan 16, 2018
📌 Commit 3a7e247 has been approved by |
…ark-Simulacrum Test rustdoc js Add tests for the rustdoc search. It was heavily required because of all the recent breaking changes that happened while I went through improvements in doc search (add search in/for generic search for example).
…ark-Simulacrum Test rustdoc js Add tests for the rustdoc search. It was heavily required because of all the recent breaking changes that happened while I went through improvements in doc search (add search in/for generic search for example).
…ark-Simulacrum Test rustdoc js Add tests for the rustdoc search. It was heavily required because of all the recent breaking changes that happened while I went through improvements in doc search (add search in/for generic search for example).
Add tests for the rustdoc search. It was heavily required because of all the recent breaking changes that happened while I went through improvements in doc search (add search in/for generic search for example).