rust/tests/ui/threads-sendsync/test-tasks-invalid-value.rs

// This checks that RUST_TEST_THREADS not being 1, 2, ... is detected
// properly.

//@ run-fail
//@ error-pattern:should be a positive integer
//@ compile-flags: --test
//@ exec-env:RUST_TEST_THREADS=foo
//@ needs-threads

#[test]
fn do_nothing() {}
RUST_TEST_TASKS -> RUST_TEST_THREADS We don't use 'task' anymore, these are now threads. Because this changes the name of a compiler option, this is [breaking-change] 2015-03-19 15:42:53 -04:00			`// This checks that RUST_TEST_THREADS not being 1, 2, ... is detected`
Make the unit-test framework check RUST_TEST_TASKS over RUST_THREADS. Fixes #7335. 2013-08-28 22:58:41 +10:00			`// properly.`

[AUTO-GENERATED] Migrate ui tests from `//` to `//@` directives 2024-02-16 20:02:50 +00:00			`//@ run-fail`
			`//@ error-pattern:should be a positive integer`
			`//@ compile-flags: --test`
			`//@ exec-env:RUST_TEST_THREADS=foo`
compiletest: Add a `//@ needs-threads` directive This commit is extracted from #122036 and adds a new directive to the `compiletest` test runner, `//@ needs-threads`. This is intended to capture the need that a target must implement threading to execute a specific test, typically one that uses `std::thread`. This is primarily done for WebAssembly targets which currently do not have threads by default. This enables transitioning a lot of `//@ ignore-wasm*`-style ignores into a more self-documenting `//@ needs-threads` directive. Additionally the `wasm32-wasi-preview1-threads` target, for example, does actually have threads, but isn't tested in CI at this time. This change enables running these tests for that target, but not other wasm targets. 2024-03-06 12:19:20 -08:00			`//@ needs-threads`
Make the unit-test framework check RUST_TEST_TASKS over RUST_THREADS. Fixes #7335. 2013-08-28 22:58:41 +10:00
			`#[test]`
			`fn do_nothing() {}`