-
Notifications
You must be signed in to change notification settings - Fork 69
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
Move tests out of src #573
Comments
This issue is not meant to be used for technical discussion. There is a Zulip stream for that. Use this issue to leave procedural comments, such as volunteering to review, indicating that you second the proposal (or third, etc), or raising a concern that you would like to be addressed. cc @rust-lang/compiler @rust-lang/compiler-contributors |
The rust-lang/rust repo is currently stuck in mid-transition with |
@rustbot label -final-comment-period +major-change-accepted |
A PR is up at rust-lang/rust#106458 |
Move src/test to the root See MCP at rust-lang/compiler-team#573 There may be more changes needed. The first commit is just the move of the files: You can check that the first commit did not do anything else than renames by running ``` git diff --diff-filter=r -M100% <rust-lang remote>/master <first commit hash> ``` The output should be empty, because the filter excludes renames, and the match threshold for qualifying a rename is 100%. The second one is mostly a "find and replace" of `src/test` to `tests` and whatever is needed to make CI pass. What is left to do: --- - [x] Move directory - [ ] Change references to `src/test` - [x] Change references in-tree - [ ] Change references in submodules / out-of-tree docs - [x] Make CI pass: - [x] Fix tidy - [x] Fix tests - [x] Bless tests if needed (shouldn't normally) - [ ] Merge it !
Move src/test to the root See MCP at rust-lang/compiler-team#573 There may be more changes needed. The first commit is just the move of the files: You can check that the first commit did not do anything else than renames by running ``` git diff --diff-filter=r -M100% <rust-lang remote>/master <first commit hash> ``` The output should be empty, because the filter excludes renames, and the match threshold for qualifying a rename is 100%. The second one is mostly a "find and replace" of `src/test` to `tests` and whatever is needed to make CI pass. What is left to do: --- - [x] Move directory - [ ] Change references to `src/test` - [x] Change references in-tree - [ ] Change references in submodules / out-of-tree docs - [x] Make CI pass: - [x] Fix tidy - [x] Fix tests - [x] Bless tests if needed (shouldn't normally) - [ ] Merge it !
Move src/test to the root See MCP at rust-lang/compiler-team#573 There may be more changes needed. The first commit is just the move of the files: You can check that the first commit did not do anything else than renames by running ``` git diff --diff-filter=r -M100% <rust-lang remote>/master <first commit hash> ``` The output should be empty, because the filter excludes renames, and the match threshold for qualifying a rename is 100%. The second one is mostly a "find and replace" of `src/test` to `tests` and whatever is needed to make CI pass. What is left to do: --- - [x] Move directory - [ ] Change references to `src/test` - [x] Change references in-tree - [ ] Change references in submodules / out-of-tree docs - [x] Make CI pass: - [x] Fix tidy - [x] Fix tests - [x] Bless tests if needed (shouldn't normally) - [ ] Merge it !
Proposal
Searching code on github only supports positive path filtering (i.e. "include path") whereas having tests inside src requires negative path filtering (i.e. "exclude path"). To make it truly usable we should move tests out of src.
Mentors or Reviewers
Process
The main points of the Major Change Process are as follows:
@rustbot second
.-C flag
, then full team check-off is required.@rfcbot fcp merge
on either the MCP or the PR.You can read more about Major Change Proposals on forge.
Comments
This issue is not meant to be used for technical discussion. There is a Zulip stream for that. Use this issue to leave procedural comments, such as volunteering to review, indicating that you second the proposal (or third, etc), or raising a concern that you would like to be addressed.
The text was updated successfully, but these errors were encountered: