-
Notifications
You must be signed in to change notification settings - Fork 12.8k
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
Adding ignore fuchsia tests for signal interpretation cases #102032
Adding ignore fuchsia tests for signal interpretation cases #102032
Conversation
6a8bdb5
to
45e258e
Compare
e6bb6d3
to
812db90
Compare
1fbad5d
to
b4383f5
Compare
@@ -2,6 +2,7 @@ | |||
// ignore-emscripten no processes | |||
// ignore-sgx no processes | |||
// ignore-windows | |||
// ignore-fuchsia code returned as ZX_TASK_RETCODE_EXCEPTION_KILL, FIXME (#109976) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There's no Fuchsia issue here; the issue is on the standard library exposing these concepts correctly, so it belongs on this Github repo. Probably you can point directly to #58590. (Short of that, which is a major change, it's possible we could map this std::os::unix::process::ExitStatusExt
API partly onto Fuchsia contexts.)
Btw, to link to the issue you created you want http://fxbug.dev/109976. A number starting with # refers to an issue in this Github repo.
src/test/ui/runtime/out-of-stack.rs
Outdated
@@ -5,6 +5,7 @@ | |||
// ignore-android: FIXME (#20004) | |||
// ignore-emscripten no processes | |||
// ignore-sgx no processes | |||
// ignore-fuchsia must translate zircon signal to SIGABRT, FIXME (#109976) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
same as above
@@ -3,6 +3,7 @@ | |||
#![allow(unused_imports)] | |||
// ignore-emscripten can't run commands | |||
// ignore-sgx no processes | |||
// ignore-fuchsia must translate zircon signal to SIGSEGV/SIGBUS, FIXME (#109976) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This test has a handler for not(unix); we can use that one for Fuchsia without disabling the test entirely.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A previous version changed those lines into:
#[cfg(all(unix, not(target_os = "fuchsia")))]
#[cfg(any(not(unix), target_os = "fuchsia"))]
Is this how I should approach the change?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah I think that's right and you could also leave a FIXME with a link to the same issue you're using for the other tests.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think that manually adding Fuchsia to the #[cfg(not(unix))]
case may cause us to forget that this test does not actually pass for Fuchsia. We have to either support this functionality or remove Fuchsia from #[cfg(unix)]
, upon which this test will pass with no modifications.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
To clarify, the test "passes" in the sense that it does not have a successful status !status.success()
, but "fails" in the sense that the signal is not what is expected (SIGSEGV/SIGBUS). I agree that this comes down to whether this is expected behavior or not for Posix-lite
b4383f5
to
9a2b5ba
Compare
9a2b5ba
to
6c29716
Compare
@bors r+ rollup |
Rollup of 12 pull requests Successful merges: - rust-lang#101952 (Avoid panicking on missing fallback) - rust-lang#102030 (Don't crate-locally reexport walk functions in tidy) - rust-lang#102032 (Adding ignore fuchsia tests for signal interpretation cases) - rust-lang#102033 (Adding needs-unwind to nicer-assert-messages compiler ui tests) - rust-lang#102054 (Unify "all items" page's sidebar with other pages) - rust-lang#102071 (Adding needs-unwind for tests testing memory size of Futures/Closures) - rust-lang#102073 (Adding ignore fuchsia tests for execvp) - rust-lang#102075 (rustdoc: remove no-op CSS `.content > .methods > .method`) - rust-lang#102079 (Update books) - rust-lang#102084 (Adding needs-unwind for test using panic::catch_unwind) - rust-lang#102100 (Prevent usage of .stab elements to create scrollable areas in doc blocks) - rust-lang#102102 (Add doc aliases on Sized trait) Failed merges: r? `@ghost` `@rustbot` modify labels: rollup
…r=tmandry Fixup failing fuchsia tests The Fuchsia platform passes all tests with these changes. Two tests are ignored because they rely on Fuchsia not returning a status code upon a process aborting. See rust-lang#102032 and rust-lang#58590 for more details on that topic. Many formatting changes are also included in this PR. r? tmandry r? erickt
Rollup merge of rust-lang#127461 - c6c7:fixup-failing-fuchsia-tests, r=tmandry Fixup failing fuchsia tests The Fuchsia platform passes all tests with these changes. Two tests are ignored because they rely on Fuchsia not returning a status code upon a process aborting. See rust-lang#102032 and rust-lang#58590 for more details on that topic. Many formatting changes are also included in this PR. r? tmandry r? erickt
Tests where Signal interpreting is required. Since Fuchsia currently does not return signals of type
libc::SIGSEGV
etc., instead, use generalized!status.success()
case.cc. @djkoloski
r? @tmandry