running `rustdoc-js-std` tests does not rebuild rustdoc even if it is dirty
Open
Nobody has claimed this yet.
A-testsuite
C-bug
T-bootstrap
- Dominant language
- Rust
- Stars
- 119k
- Forks
- 16.1k
- PR merge metrics
- PR metrics pending
Description
reproduction steps:
./x test -v tests/rustdoc-js-std/return-based-sort.js(or any other unit test in the folder, probably)- make a change to
search.js(one that impacts the result of the test will make it more obvious) ./x test -v tests/rustdoc-js-std/return-based-sort.js(again)
rustdoc will not get rebuilt.
i've run into this a few times before but i only now figured out what was happening (i think?).
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce with ./x test -v tests/rustdoc-js-std/return-based-sort.js, then modify search.js and run the same test again. Trace how this test is selected and how rustdoc rebuild decisions are made. Done means the second run rebuilds rustdoc and reflects the search.js change in the test result.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- build-system, compilers, testing-qa
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100