-
Notifications
You must be signed in to change notification settings - Fork 12.9k
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
Add needs-unwind
and beginning of support for testing panic=abort
std to compiletest
#84734
Conversation
This comment has been minimized.
This comment has been minimized.
b01f6a5
to
64b9061
Compare
This comment has been minimized.
This comment has been minimized.
64b9061
to
c65ba57
Compare
This comment has been minimized.
This comment has been minimized.
4e16d2e
to
9cda465
Compare
Are you sure those are all the tests that need it? For cg_clif I get a much larger set of tests: https://github.com/bjorn3/rustc_codegen_cranelift/blob/6d30315d055e92464026c2ac0d7f3ad8b02539b6/scripts/test_rustc_tests.sh#L13-L16 and https://github.com/bjorn3/rustc_codegen_cranelift/blob/6d30315d055e92464026c2ac0d7f3ad8b02539b6/scripts/test_rustc_tests.sh#L24-L41 |
@bjorn3 ah it's because I disabled running any of the UI tests. I should build a |
needs-unwind
and support for testing panic=abort
libstd to compiletestneeds-unwind
and beginning of support for testing panic=abort
std to compiletest
This seems good to me; I imagine it may make sense to add the support and then actually annotate all the tests in followup PRs. I left a nit, but please make sure to squash it into the existing commits. With regards to future extensions (e.g., multiple target variants, etc.) I think support for configuring the panic strategy desired seems OK, but allowing one to build multiple 'identical' targets but with different panic strategies or other attributes is probably best left out of scope for now. It may become (more) desirable as we gain further support for build-std or similar features, where it may make sense to "prebuild" std for a variety of configurations, so that users can opt-in via some standard mechanism to those builds, perhaps before we allow them to actually build std themselves. |
I just need this until rustbuild supports -Cpanic=abort std directly.
9cda465
to
947ad58
Compare
Let me know what strategy you want to take with the annotations, but r=me on this first draft of you want to followup with those |
@Mark-Simulacrum Yes, I'd prefer to do those in a follow-up. I also want to make sure that these have a way of being tested in CI (probably as part of the wasm target) @bors r=Mark-Simulacrum |
📌 Commit 947ad58 has been approved by |
…=Mark-Simulacrum Add `needs-unwind` and beginning of support for testing `panic=abort` std to compiletest For the Fuchsia platform we build libstd with `panic=abort` and would like a way to run tests with that enabled. This adds low-level support for this directly to compiletest. In the future I'd like to add high-level support in rustbuild, e.g. having target-specific flags that allow configuring a panic strategy. (Side note: It would be nice if we could also build multiple configurations for the same target, but I'm getting ahead of myself.) This plus rust-lang#84500 have everything that's needed to get ui tests passing on fuchsia targets. Part of rust-lang#84766. Note that this change only includes the header on tests which need an unwinder to _build_, not those which need it to _run_. r? `@Mark-Simulacrum`
…=Mark-Simulacrum Add `needs-unwind` and beginning of support for testing `panic=abort` std to compiletest For the Fuchsia platform we build libstd with `panic=abort` and would like a way to run tests with that enabled. This adds low-level support for this directly to compiletest. In the future I'd like to add high-level support in rustbuild, e.g. having target-specific flags that allow configuring a panic strategy. (Side note: It would be nice if we could also build multiple configurations for the same target, but I'm getting ahead of myself.) This plus rust-lang#84500 have everything that's needed to get ui tests passing on fuchsia targets. Part of rust-lang#84766. Note that this change only includes the header on tests which need an unwinder to _build_, not those which need it to _run_. r? ``@Mark-Simulacrum``
…=Mark-Simulacrum Add `needs-unwind` and beginning of support for testing `panic=abort` std to compiletest For the Fuchsia platform we build libstd with `panic=abort` and would like a way to run tests with that enabled. This adds low-level support for this directly to compiletest. In the future I'd like to add high-level support in rustbuild, e.g. having target-specific flags that allow configuring a panic strategy. (Side note: It would be nice if we could also build multiple configurations for the same target, but I'm getting ahead of myself.) This plus rust-lang#84500 have everything that's needed to get ui tests passing on fuchsia targets. Part of rust-lang#84766. Note that this change only includes the header on tests which need an unwinder to _build_, not those which need it to _run_. r? ```@Mark-Simulacrum```
Rollup of 11 pull requests Successful merges: - rust-lang#84409 (Ensure TLS destructors run before thread joins in SGX) - rust-lang#84500 (Add --run flag to compiletest) - rust-lang#84728 (Add test for suggestion to borrow unsized function parameters) - rust-lang#84734 (Add `needs-unwind` and beginning of support for testing `panic=abort` std to compiletest) - rust-lang#84755 (Allow using `core::` in intra-doc links within core itself) - rust-lang#84871 (Disallows `#![feature(no_coverage)]` on stable and beta (using standard crate-level gating)) - rust-lang#84872 (Wire up tidy dependency checks for cg_clif) - rust-lang#84896 (Handle incorrect placement of parentheses in trait bounds more gracefully) - rust-lang#84905 (CTFE engine: rename copy → copy_intrinsic, move to intrinsics.rs) - rust-lang#84953 (Remove unneeded call to with_default_session_globals in rustdoc highlight) - rust-lang#84987 (small nits) Failed merges: r? `@ghost` `@rustbot` modify labels: rollup
For the Fuchsia platform we build libstd with
panic=abort
and would like a way to run tests with that enabled. This adds low-level support for this directly to compiletest.In the future I'd like to add high-level support in rustbuild, e.g. having target-specific flags that allow configuring a panic strategy. (Side note: It would be nice if we could also build multiple configurations for the same target, but I'm getting ahead of myself.)
This plus #84500 have everything that's needed to get ui tests passing on fuchsia targets.
Part of #84766. Note that this change only includes the header on tests which need an unwinder to build, not those which need it to run.
r? @Mark-Simulacrum