about summary refs log tree commit diff
path: root/src/libsyntax_ext
diff options
context:
space:
mode:
authorMazdak Farrokhzad <twingoow@gmail.com>2019-11-15 18:02:01 +0100
committerGitHub <noreply@github.com>2019-11-15 18:02:01 +0100
commit4e6e1eccf1e512d1dee42ddad007b94f17b6e2de (patch)
tree8f889a71b3af7e66bd8722fedd8b79d6fa640ae0 /src/libsyntax_ext
parente3c78d549e0d8cdd3c05190e93f4ec7ff09a9ed1 (diff)
parentd252ba35d490f16d2efefdedc581b1c9d6d64ecb (diff)
downloadrust-4e6e1eccf1e512d1dee42ddad007b94f17b6e2de.tar.gz
rust-4e6e1eccf1e512d1dee42ddad007b94f17b6e2de.zip
Rollup merge of #66415 - tmandry:force-test-in-process, r=alexcrichton
Add --force-run-in-process unstable option to libtest

When running tests with `-Zpanic_abort_tests`, it's sometimes desirable to fall back to the old behavior of only running tests in-process. This comes in handy if the system process launcher is unavailable, or the test code somehow expects all tests to be run in the same process.

For example, in Fuchsia we have unit tests that actually test the process launcher itself, in which case we can't use the process launcher to run the tests :).

r? @alexcrichton
cc @cramertj,@petrhosek
Diffstat (limited to 'src/libsyntax_ext')
-rw-r--r--src/libsyntax_ext/test_harness.rs3
1 files changed, 2 insertions, 1 deletions
diff --git a/src/libsyntax_ext/test_harness.rs b/src/libsyntax_ext/test_harness.rs
index 1492f6f575f..659780d7a43 100644
--- a/src/libsyntax_ext/test_harness.rs
+++ b/src/libsyntax_ext/test_harness.rs
@@ -67,7 +67,8 @@ pub fn inject(
                 PanicStrategy::Unwind
             }
             (PanicStrategy::Abort, false) => {
-                span_diagnostic.err("building tests with panic=abort is not yet supported");
+                span_diagnostic.err("building tests with panic=abort is not supported \
+                                     without `-Zpanic_abort_tests`");
                 PanicStrategy::Unwind
             }
             (PanicStrategy::Unwind, _) => PanicStrategy::Unwind,