diff options
| author | Manish Goregaokar <manishsmail@gmail.com> | 2015-02-23 14:43:44 +0530 |
|---|---|---|
| committer | Manish Goregaokar <manishsmail@gmail.com> | 2015-02-23 14:43:44 +0530 |
| commit | 1acd7c9fe15798c1efc87ba5070950af6f03b64f (patch) | |
| tree | 9080844b147d647809292cbfb51bd89cddcecd5a /src/test/codegen/stack-alloc-string-slice.rs | |
| parent | 46a545100a00065570be58ffb4c8ea8cc1a17bc8 (diff) | |
| parent | ef1308c407c34d91d176f1de6c0f86ecbea615f4 (diff) | |
| download | rust-1acd7c9fe15798c1efc87ba5070950af6f03b64f.tar.gz rust-1acd7c9fe15798c1efc87ba5070950af6f03b64f.zip | |
Rollup merge of #22371 - fhahn:issue-17829-compiletest-nocapture, r=Manishearth
This is a patch for #17829. In `compiletest` there are multiple layers which capture the output. The first layer is `run_tests_console` which is used to execute all tests. Then there are some tests that contain unit tests, which by default also captures output. Therefore `compiletest` adds `RUST_TEST_NOCAPTURE` (and `RUST_TEST_TASKS` for completeness) to the run environment of the task. Finally, the task used to execute a test redirects stdout and stdin. At the moment, the `VERBOSE=1` prints all captured output of the task (but has to print stdout and stderr separately). So at the moment using `RUST_TEST_NOCAPTURE=1` only makes sense when also using `VERBOSE=1` which seems a little bit cumbersome. Should I update the patch to only print the output of the tasks that actually execute the test (`VERBOSE=1` includes other stuff, like the output of the task used to compile the test)? This will probably involve adding an extra flag to some functions in `src/compiletest/runtest.rs` to distinguish compilation runs from runs that execute the actual tests.
Diffstat (limited to 'src/test/codegen/stack-alloc-string-slice.rs')
0 files changed, 0 insertions, 0 deletions
