Uh oh!
There was an error while loading. Please reload this page.
tests/ui/issues/: The Issues Strike Back [1/N] - #144151
Conversation
rustbot
commented
Jul 18, 2025
|
rustbot
commented
Jul 18, 2025
There are changes to the cc @jieyouxu |
This comment has been minimized.
This comment has been minimized.
tests/ui/issues/: The Part Where I Reorganize You [1/N]tests/ui/issues/: The Issues Strike Back [1/N]asquared31415
commented
Jul 19, 2025
I have not been following this very much, but that's amazing that there's already been over 150 tests removed from the |
bors
commented
Jul 23, 2025
☔ The latest upstream changes (presumably #144360) made this pull request unmergeable. Please resolve the merge conflicts. |
There was a problem hiding this comment.
Thanks, some nits.
Re. naming for these issues tests, I think it's actually better to still include the test number (not the substring issue of course) unless there's a very descriptive and specific test name.
Test names like *-type-error or *-error or *-behavior are super generic, and since they're not the kind of "foundational" test coverage (where you intentionally "build up" systematic test coverage for something), they would IMO benefit from having the issue number for more context upfront.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Next PRs imo should be general better, but only thing is I didn't used issue numbers anywhere, this is most problem I see for now. I will address this problem in the future |
jieyouxu
commented
Jul 24, 2025
That's fine :) |
rustbot
commented
Jul 24, 2025
This PR modifies |
It'll fail because of stray .stderr files, very soon |
jieyouxu
commented
Jul 24, 2025
No rush :) It's 🛏️ time for me, so I'll re-review another time. |
There also will be a PR after I finish with this one where I rename all directories with |
This comment has been minimized.
This comment has been minimized.
Kivooeo
commented
Jul 24, 2025
@rustbot ready |
There was a problem hiding this comment.
Let's wait until it's merged then I'll fix conflict and we are good, also I'm going to revise other parts names, to add issue numbers at some generic names
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
jieyouxu
commented
Jul 25, 2025
Hm yeah, some of these test names are IMO still too generic, that they really could use the issue number for more TL;DR context. |
rustbot
commented
Jul 25, 2025
Reminder, once the PR becomes ready for a review, use |
3453826 to
2ee2a2fComparejieyouxu
commented
Jul 25, 2025
bors
commented
Jul 25, 2025
☔ The latest upstream changes (presumably #144440) made this pull request unmergeable. Please resolve the merge conflicts. |
Kivooeo
commented
Jul 25, 2025
@rustbot ready |
jieyouxu
commented
Jul 28, 2025
@bors r+ rollup |
bors
commented
Jul 28, 2025
Rollup of 7 pull requests Successful merges: - #144072 (update `Atomic*::from_ptr` and `Atomic*::as_ptr` docs) - #144151 (`tests/ui/issues/`: The Issues Strike Back [1/N]) - #144300 (Clippy fixes for miropt-test-tools) - #144399 (Add a ratchet for moving all standard library tests to separate packages) - #144472 (str: Mark unstable `round_char_boundary` feature functions as const) - #144503 (Various refactors to the codegen coordinator code (part 3)) - #144530 (coverage: Infer `instances_used` from `pgo_func_name_var_map`) r? `@ghost` `@rustbot` modify labels: rollup
Uh oh!
There was an error while loading. Please reload this page.
Rollup merge of #144151 - Kivooeo:issue1, r=jieyouxu `tests/ui/issues/`: The Issues Strike Back [1/N] I believe I’ve finally brought [my program](https://github.com/Kivooeo/test-manager) to life -- it now handles multiple test moves in one go: plain moves first, then a gentle touch on each file depends on given options. The process should be much smoother now. Of course, I won’t rush through everything in a few days -- that would be unkind to `@Oneirical.` I’ll pace myself. And also I can't have more than one such PR because `issues.txt` will conflict with previous parts after merging them which is not fun as well. This PR is just that: first commit - moves; second - regression comments and the occasional .stderr reblesses, also issue.txt and tidy changes. Nothing special, but progress nonetheless. This is for the purpose of preserving test file history during restructuring Part of #133895. r? `@jieyouxu`
Rollup of 7 pull requests Successful merges: - rust-lang/rust#144072 (update `Atomic*::from_ptr` and `Atomic*::as_ptr` docs) - rust-lang/rust#144151 (`tests/ui/issues/`: The Issues Strike Back [1/N]) - rust-lang/rust#144300 (Clippy fixes for miropt-test-tools) - rust-lang/rust#144399 (Add a ratchet for moving all standard library tests to separate packages) - rust-lang/rust#144472 (str: Mark unstable `round_char_boundary` feature functions as const) - rust-lang/rust#144503 (Various refactors to the codegen coordinator code (part 3)) - rust-lang/rust#144530 (coverage: Infer `instances_used` from `pgo_func_name_var_map`) r? `@ghost` `@rustbot` modify labels: rollup
I believe I’ve finally brought my program to life -- it now handles multiple test moves in one go: plain moves first, then a gentle touch on each file depends on given options. The process should be much smoother now.
Of course, I won’t rush through everything in a few days -- that would be unkind to @Oneirical. I’ll pace myself. And also I can't have more than one such PR because
issues.txtwill conflict with previous parts after merging them which is not fun as well.This PR is just that: first commit - moves; second - regression comments and the occasional .stderr reblesses, also issue.txt and tidy changes. Nothing special, but progress nonetheless. This is for the purpose of preserving test file history during restructuring
Part of #133895.
r? @jieyouxu