Clean up some uses of logging in ui tests

This commit is contained in:
Oliver Scherer 2020-07-25 18:36:44 +02:00
parent 73ca84dfa1
commit 79c0db4cc8
5 changed files with 9 additions and 19 deletions

View File

@ -1,5 +1,5 @@
// run-pass
// exec-env:RUSTC_LOG=rustc::middle=debug
// rustc-env:RUSTC_LOG=rustc::middle=debug
fn main() {
let b = 1isize;

View File

@ -1,7 +1,6 @@
// run-pass
// ignore-windows
// ignore-emscripten no threads support
// exec-env:RUSTC_LOG=debug
use std::cell::Cell;
use std::fmt;
@ -19,10 +18,13 @@ impl fmt::Debug for Foo {
}
pub fn main() {
thread::spawn(move|| {
thread::spawn(move || {
let mut f = Foo(Cell::new(0));
println!("{:?}", f);
let Foo(ref mut f) = f;
assert_eq!(f.get(), 1);
}).join().ok().unwrap();
})
.join()
.ok()
.unwrap();
}

View File

@ -1,12 +0,0 @@
// run-pass
// exec-env:RUSTC_LOG=std::ptr
// In issue #9487, it was realized that std::ptr was invoking the logging
// infrastructure, and when std::ptr was used during runtime initialization,
// this caused some serious problems. The problems have since been fixed, but
// this test will trigger "output during runtime initialization" to make sure
// that the bug isn't re-introduced.
// pretty-expanded FIXME #23616
pub fn main() {}

View File

@ -2,7 +2,7 @@
#![allow(unused_must_use)]
#![allow(unused_mut)]
// ignore-windows
// exec-env:RUSTC_LOG=debug
// exec-env:RUST_LOG=debug
// ignore-emscripten no threads support
// regression test for issue #10405, make sure we don't call println! too soon.
@ -11,5 +11,5 @@ use std::thread::Builder;
pub fn main() {
let mut t = Builder::new();
t.spawn(move|| ());
t.spawn(move || ());
}

View File

@ -623,7 +623,7 @@ impl<'test> TestCx<'test> {
.arg("-L")
.arg(&aux_dir)
.args(&self.props.compile_flags)
.envs(self.props.exec_env.clone());
.envs(self.props.rustc_env.clone());
self.maybe_add_external_args(
&mut rustc,
self.split_maybe_args(&self.config.target_rustcflags),