os-rust/src/test/run-pass/exec-env.rs

// exec-env:TEST_EXEC_ENV=22
// ignore-cloudabi no env vars
// ignore-emscripten FIXME: issue #31622

use std::env;

pub fn main() {
    assert_eq!(env::var("TEST_EXEC_ENV"), Ok("22".to_string()));
}
add option exec-env to set env variables during test execution 2012-04-13 09:19:07 -07:00			`// exec-env:TEST_EXEC_ENV=22`
Add 'ignore-cloudabi' to tests that don't and won't build on CloudABI. It looks like many of these tests are already disabled on emscripten, which also doesn't seem to support environment variables and subprocess spawning. Just add a similar tag for CloudABI. While there, sort some of the lists of operating systems alphabetically. 2018-01-02 14:11:41 +01:00			`// ignore-cloudabi no env vars`
[emscripten] Ignore tests Most of these rely on spawning processes, which is not possible in Emscripten. 2016-08-09 01:39:37 +02:00			`// ignore-emscripten FIXME: issue #31622`
rustdoc: Replace no-pretty-expanded with pretty-expanded Now that features must be declared expanded source often does not compile. This adds 'pretty-expanded' to a bunch of test cases that still work. 2015-03-22 13:13:15 -07:00
Cleanup getenv from tests and benchmarks 2015-02-13 22:08:05 +02:00			`use std::env;`
librustc: Stop reexporting the standard modules from prelude. 2013-05-24 19:35:29 -07:00
check-fast fallout from removing export, r=burningtree 2013-02-01 19:43:17 -08:00			`pub fn main() {`
Cleanup getenv from tests and benchmarks 2015-02-13 22:08:05 +02:00			`assert_eq!(env::var("TEST_EXEC_ENV"), Ok("22".to_string()));`
add option exec-env to set env variables during test execution 2012-04-13 09:19:07 -07:00			`}`