rust/tests/ui/process/tls-exit-status.rs

//@ run-fail
//@ error-pattern:nonzero
//@ exec-env:RUST_NEWRT=1
//@ ignore-wasm32 no processes

use std::env;

fn main() {
    env::args();
    panic!("please have a nonzero exit status");
}
[AUTO-GENERATED] Migrate ui tests from `//` to `//@` directives 2024-02-16 20:02:50 +00:00			`//@ run-fail`
			`//@ error-pattern:nonzero`
			`//@ exec-env:RUST_NEWRT=1`
Update test directives for `wasm32-wasip1` * The WASI targets deal with the `main` symbol a bit differently than native so some `codegen` and `assembly` tests have been ignored. * All `ignore-emscripten` directives have been updated to `ignore-wasm32` to be more clear that all wasm targets are ignored and it's not just Emscripten. * Most `ignore-wasm32-bare` directives are now gone. * Some ignore directives for wasm were switched to `needs-unwind` instead. * Many `ignore-wasm32*` directives are removed as the tests work with WASI as opposed to `wasm32-unknown-unknown`. 2024-03-06 12:44:54 -08:00			`//@ ignore-wasm32 no processes`
Add tests for issues which can be closed Closes #5275, $4547 2013-07-19 19:01:46 -07:00
Replace some uses of deprecated os functions This commit mostly replaces some of the uses of os::args with env::args. 2015-02-16 16:04:02 +02:00			`use std::env;`
Add tests for issues which can be closed Closes #5275, $4547 2013-07-19 19:01:46 -07:00
			`fn main() {`
Replace some uses of deprecated os functions This commit mostly replaces some of the uses of os::args with env::args. 2015-02-16 16:04:02 +02:00			`env::args();`
Rename fail! to panic! https://github.com/rust-lang/rfcs/pull/221 The current terminology of "task failure" often causes problems when writing or speaking about code. You often want to talk about the possibility of an operation that returns a Result "failing", but cannot because of the ambiguity with task failure. Instead, you have to speak of "the failing case" or "when the operation does not succeed" or other circumlocutions. Likewise, we use a "Failure" header in rustdoc to describe when operations may fail the task, but it would often be helpful to separate out a section describing the "Err-producing" case. We have been steadily moving away from task failure and toward Result as an error-handling mechanism, so we should optimize our terminology accordingly: Result-producing functions should be easy to describe. To update your code, rename any call to `fail!` to `panic!` instead. Assuming you have not created your own macro named `panic!`, this will work on UNIX based systems: grep -lZR 'fail!' . \| xargs -0 -l sed -i -e 's/fail!/panic!/g' You can of course also do this by hand. [breaking-change] 2014-10-09 15:17:22 -04:00			`panic!("please have a nonzero exit status");`
Add tests for issues which can be closed Closes #5275, $4547 2013-07-19 19:01:46 -07:00			`}`