redesign stage 0 std follow-ups#141914
Conversation
jieyouxu
left a comment
There was a problem hiding this comment.
Looks good to me modulo changelog entry and a nit.
Consistent with what we discussed in #t-infra/bootstrap > Stage 0 std redesign support thread @ 💬.
This comment has been minimized.
This comment has been minimized.
6692543 to
118eb4c
Compare
|
This PR modifies If appropriate, please update |
| RUN sh /scripts/sccache.sh | ||
|
|
||
| ENV SCRIPT \ | ||
| python3 ../x.py check --stage 0 && \ |
There was a problem hiding this comment.
I am not entirely sure about this yet. If it makes the pipeline too long, we can consider moving it to some other PR pipeline.
There was a problem hiding this comment.
It still seems to be roughly the same duration as mingw-check-1 (only about 3.5 minutes longer).
There was a problem hiding this comment.
Not needed anymore. It's still needed actually. I will keep it.
This comment has been minimized.
This comment has been minimized.
|
For a second opinion of hard-error on check library at explicit stage 0. |
|
If I want to check the standard library, how would I do so with this PR? |
|
|
@rustbot ready |
|
We probably want some quicker action on this. r? Kobzol |
Kobzol
left a comment
There was a problem hiding this comment.
Left some comments, but if we switch the default stage of check back to 0, it won't be relevant anymore, I guess :)
| RUN sh /scripts/sccache.sh | ||
|
|
||
| ENV SCRIPT \ | ||
| python3 ../x.py check --stage 0 && \ |
Signed-off-by: onur-ozkan <work@onurozkan.dev>
I thought the same, but then I realized that we run |
| if is_explicitly_called { | ||
| eprintln!("WARNING: stage 0 std is precompiled and does nothing during `x check`."); | ||
| } |
There was a problem hiding this comment.
Should we give this warning unconditionally, or keep it as it is?
There was a problem hiding this comment.
I would only keep it when the library was explicitly requested, so this seems fine.
This is changed. To check library, you should either do cc @bjorn3 |
|
Looks good. You can r=me once CI is green. |
Signed-off-by: onur-ozkan <work@onurozkan.dev>
Signed-off-by: onur-ozkan <work@onurozkan.dev>
Updated again (sorry). Now you just need to run |
This was pushed after you approved the PR. Are you okay with that commit as well? |
Signed-off-by: onur-ozkan <work@onurozkan.dev>
|
Yeah, I'm fine with that. |
|
@bors r+ r=Kobzol |
|
I think I have never seen bors duplicating the merge message before. 🤔 |
You wrote r+ and r= :D |
|
lol, seems like I didn't sleep enough |
Rollup of 8 pull requests Successful merges: - #141724 (fix(#141141): When expanding `PartialEq`, check equality of scalar types first.) - #141833 (`tests/ui`: A New Order [2/N]) - #141861 (Switch `x86_64-msvc-{1,2}` back to Windows Server 2025 images) - #141914 (redesign stage 0 std follow-ups) - #141918 (Deconstruct values in the THIR visitor) - #141923 (Update books) - #141931 (Deconstruct values in the THIR visitor) - #141956 (Remove two trait methods from cg_ssa) r? `@ghost` `@rustbot` modify labels: rollup
Rollup of 8 pull requests Successful merges: - rust-lang/rust#141724 (fix(rust-lang/rust#141141): When expanding `PartialEq`, check equality of scalar types first.) - rust-lang/rust#141833 (`tests/ui`: A New Order [2/N]) - rust-lang/rust#141861 (Switch `x86_64-msvc-{1,2}` back to Windows Server 2025 images) - rust-lang/rust#141914 (redesign stage 0 std follow-ups) - rust-lang/rust#141918 (Deconstruct values in the THIR visitor) - rust-lang/rust#141923 (Update books) - rust-lang/rust#141931 (Deconstruct values in the THIR visitor) - rust-lang/rust#141956 (Remove two trait methods from cg_ssa) r? `@ghost` `@rustbot` modify labels: rollup
Various follow-ups pointed out on Zulip during post-merge discussions of redesign stage 0 std #119899.
r? @jieyouxu
Fixes #141902.
Fixes #141905.
cc @jyn514