-
Notifications
You must be signed in to change notification settings - Fork 12.7k
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
Check the docs as part of check-stageN #31689
Conversation
Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @brson (or someone else) soon. If any changes to this PR are deemed necessary, please add them as extra commits. This ensures that the reviewer can see what has changed since they last reviewed the code. Due to the way GitHub handles out-of-date commits, this should also make it reasonably obvious what issues have or haven't been addressed. Large or tricky changes may require several passes of review and changes. Please see the contribution instructions for more information. |
Looking again it looks like
? |
To answer my own question, avoiding a full rebuild on Makefile changes can
|
Perhaps this might be most appropriate behind the |
make check
Hi, that's a good idea, I've updated the branch to add check-stageN-docs to |
IIRC, something was wrong with |
Ah, it looks like it might build the error generator from stage2. |
In the case of |
https://gist.github.com/james-w/6d88ee407f2fd180c04d is the output of |
These doc dependencies are also specified here. I think what should be done is that the new |
Closing due to inactivity, but feel free to resubmit with comments addressed! |
This addresses #31587 by adding check-stage2-docs as a dependency
of make check.
With this change
make check
output showsI'm not entirely sure this is the right fix, we may instead want to depend
on a slightly more specific target, but I'm not sure what the
expected behaviour of each target is. Running all the docs tests
on
make check
seems perfectly reasonable, and the dependenciesshould mean there is no duplicated work.
If you do suggest a change I would appreciate it if you could also
let me know if there's a trick to avoid the process from deleting
all the build artefacts if the makefiles are changed. A simple tweak
to this rule means that I have to rebuild all of rust to test it. If there's
a way to avoid running get-snapshot then I would like to know,
because NO_REBUILD=1 doesn't seem to be it.
This is my first PR for rust, so I likely missed some simple things
(commit message template, NEWS entry?) Please let me know
what they are and I will happily adjust my submission.
Thanks,
James