-
Notifications
You must be signed in to change notification settings - Fork 13.4k
test-float-parse: apply cfg(not(bootstrap))
#141904
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
Conversation
Prior to stage 0 redesign, `test-float-parse` ran against in-tree std but now it runs against beta std. `f16::FromStr` were only present in in-tree std and not yet beta std, so apply `cfg(not(bootstrap))` gating to unbrick `./x check --stage=0`.
cfg(not(bootstrap))
cfg(not(bootstrap))
This makes |
@bors r+ rollup |
No objection to the change here to unblock things, but it seems a bit unusual that this tool tests the beta std at all. Is there any way to change it to run on in-tree std with the beta and in-tree compilers? |
Tracked in #141920 |
Rollup of 5 pull requests Successful merges: - #141767 (ci: use free runner for aarch64-gnu-llvm-19-1 PR job) - #141858 (Fix typo in `StructuralPartialEq` docs) - #141865 (Optionally don't steal the THIR) - #141874 (add f16_epsilon and f128_epsilon diagnostic items) - #141904 (test-float-parse: apply `cfg(not(bootstrap))`) r? `@ghost` `@rustbot` modify labels: rollup
Rollup merge of #141904 - jieyouxu:test-float-parse, r=Mark-Simulacrum test-float-parse: apply `cfg(not(bootstrap))` Prior to stage 0 redesign, `test-float-parse` ran against in-tree std but now it runs against beta std. `f16::FromStr` is only present in in-tree std and not yet beta std, so apply `cfg(not(bootstrap))` gating to unbrick `./x check --stage=0`. Fixes #141900. `./x check --stage=0` in CI is intended for follow-up. r? `@Mark-Simulacrum` (or bootstrap/libs) cc `@tgross35`
Rollup of 5 pull requests Successful merges: - rust-lang/rust#141767 (ci: use free runner for aarch64-gnu-llvm-19-1 PR job) - rust-lang/rust#141858 (Fix typo in `StructuralPartialEq` docs) - rust-lang/rust#141865 (Optionally don't steal the THIR) - rust-lang/rust#141874 (add f16_epsilon and f128_epsilon diagnostic items) - rust-lang/rust#141904 (test-float-parse: apply `cfg(not(bootstrap))`) r? `@ghost` `@rustbot` modify labels: rollup
@tgross35 just to clarify: nearly all bootstrap components support being checked at any stage. for example, (this particular component is weird because it's only to support the standard library. so probably it shouldn't support being built at stage 0, because there's no reason for it to do so, we don't build it against beta. i don't know enough about this tool to say that for sure though.) |
That's great to know!
That sounds accurate to me - I think this tool's default stage should be 1 (like std would be I think?) and then maybe give a warning when manually run with stage 0, if that's possible possible. |
Prior to stage 0 redesign,
test-float-parse
ran against in-tree std but now it runs against beta std.f16::FromStr
is only present in in-tree std and not yet beta std, so applycfg(not(bootstrap))
gating to unbrick./x check --stage=0
.Fixes #141900.
./x check --stage=0
in CI is intended for follow-up.r? @Mark-Simulacrum (or bootstrap/libs)
cc @tgross35