Conversation
|
r? @JohnTitor rustbot has assigned @JohnTitor. Use Why was this reviewer chosen?The reviewer was selected based on:
|
|
Also, remove the comments describing what the test is doing if the test is simple enough. However, keep an issue link and add a new line between your comment and the test. Here's an example of what the test could look like: #152732. |
This comment has been minimized.
This comment has been minimized.
| @@ -1,3 +1,5 @@ | |||
| // https://github.com/rust-lang/rust/issues/4265 | |||
There was a problem hiding this comment.
This should not be moved to ui/traits, there are no traits involved at all.
There was a problem hiding this comment.
Maybe put this in ui/methods instead?
|
@rustbot author |
|
Reminder, once the PR becomes ready for a review, use |
This comment has been minimized.
This comment has been minimized.
f0c2376 to
24c516f
Compare
This comment has been minimized.
This comment has been minimized.
|
@rustbot ready |
What do you mean by that |
This comment has been minimized.
This comment has been minimized.
|
I was referring to the @rustbot bless command. |
|
there is no CI-bless command or any way to do so... I think the best way you can do is run |
|
Oh, I see. You can't run the compile test because you can't build the library. In that case, I could try pushing these changes directly into your branch. I'm not sure how feasible this is for GSoC, but we could give you access to our cloud computing if you were chosen for the project. |
24c516f to
42250a2
Compare
|
Hey @Kivooeo and @cyrgani! I rectified the issues I was facing in my local Windows (regarding the STATUS_ACCESS_VIOLATION issues ) by performing a full Stage 1 Bootstrap and then blessing the 7 folders in tests/ui. |
|
@rustbot ready |
42250a2 to
1a8e127
Compare
|
@rustbot ready |
|
can you squash the commits the way i explained in comment below, it's so hard to review at current state this comment should be clear enough #149411 (comment) to make it correct, if not - please, ask questions |
|
@rustbot author |
1a8e127 to
7158f89
Compare
|
Some changes occurred in compiler/rustc_attr_parsing cc @jdonszelmann, @JonathanBrouwer Some changes occurred in compiler/rustc_hir/src/attrs cc @jdonszelmann, @JonathanBrouwer Some changes occurred in compiler/rustc_passes/src/check_attr.rs cc @jdonszelmann, @JonathanBrouwer These commits modify the If this was unintentional then you should revert the changes before this PR is merged. |
This comment has been minimized.
This comment has been minimized.
-Rename tests for clarity. -Add issue links and descriptions. -Clean up formatting and comments.
7158f89 to
95b0165
Compare
|
This PR was rebased onto a different main commit. Here's a range-diff highlighting what actually changed. Rebasing is a normal part of keeping PRs up to date, so no action is needed—this note is just to help reviewers. |
|
Thanks for pointing this out. I've squashed the commits the way said in comment on #149411. |
|
@rustbot ready |
|
move and rename in first commit and everything that touches its content in second (comment, bless, fmt, etc.) |
| @@ -1,3 +1,5 @@ | |||
| // https://github.com/rust-lang/rust/issues/4736 | |||
There was a problem hiding this comment.
I don't think this belongs in ui/typeck. ui/structs seems more appropriate.
| @@ -1,3 +1,5 @@ | |||
| // https://github.com/rust-lang/rust/issues/4265 | |||
There was a problem hiding this comment.
Maybe put this in ui/methods instead?
View all comments
Reorganize 11 tests in tests/ui/issues to appropriate subdirectories
This PR reorganizes tests in tests/ui/issues folder following the workflow suggested in the comment on #149411
Workflow:
All tests pass tidy locally using
python x.py test tidy