Sep 04 04:06:42.034 INFO checking test-logger-0.1.0 against try#5fe695a3844714c70e8f7731a553f7947987a68a for pr-53913
Sep 04 04:06:42.034 INFO running: cargo +5fe695a3844714c70e8f7731a553f7947987a68a-alt check --frozen --all --all-targets
Sep 04 04:06:42.034 INFO running `"docker" "create" "-v" "/home/ec2-user/crater/./work/local/test-source/worker-3/pr-53913/try#5fe695a3844714c70e8f7731a553f7947987a68a:/source:ro,Z" "-v" "/home/ec2-user/crater/./work/local/target-dirs/pr-53913/worker-3/try#5fe695a3844714c70e8f7731a553f7947987a68a:/target:rw,Z" "-v" "/home/ec2-user/crater/./work/local/cargo-home:/cargo-home:ro,Z" "-v" "/home/ec2-user/crater/./work/local/rustup-home:/rustup-home:ro,Z" "-e" "USER_ID=500" "-e" "CMD=cargo +5fe695a3844714c70e8f7731a553f7947987a68a-alt check --frozen --all --all-targets" "-e" "CARGO_INCREMENTAL=0" "-e" "RUST_BACKTRACE=full" "-e" "RUSTFLAGS=--cap-lints=forbid" "-m" "2G" "crater"`
Sep 04 04:06:42.214 INFO blam! cc89f5307b07f3a18523ab3543c9021301a9322faf6071f411f71383e3a7c845
Sep 04 04:06:42.216 INFO running `"docker" "start" "-a" "cc89f5307b07f3a18523ab3543c9021301a9322faf6071f411f71383e3a7c845"`
Sep 04 04:06:42.793 INFO kablam!     Checking test-logger v0.1.0 (file:///source)
Sep 04 04:06:44.207 INFO kablam! error[E0659]: `test` is ambiguous
Sep 04 04:06:44.207 INFO kablam!   --> tests/should_pass.rs:14:1
Sep 04 04:06:44.207 INFO kablam!    |
Sep 04 04:06:44.207 INFO kablam! 14 | / test!(passing_test_should_never_have_its_output_printed, {
Sep 04 04:06:44.207 INFO kablam! 15 | |     assert_eq!(99, get_some_value());
Sep 04 04:06:44.207 INFO kablam! 16 | | });
Sep 04 04:06:44.207 INFO kablam!    | |___^
Sep 04 04:06:44.207 INFO kablam!    |
Sep 04 04:06:44.208 INFO kablam! note: `test` could refer to the name imported here
Sep 04 04:06:44.208 INFO kablam!   --> tests/should_pass.rs:1:1
Sep 04 04:06:44.208 INFO kablam!    |
Sep 04 04:06:44.208 INFO kablam! 1  | #[macro_use]
Sep 04 04:06:44.208 INFO kablam!    | ^^^^^^^^^^^^
Sep 04 04:06:44.208 INFO kablam! note: `test` could also refer to the name defined here
Sep 04 04:06:44.208 INFO kablam!   --> tests/should_pass.rs:14:1
Sep 04 04:06:44.208 INFO kablam!    |
Sep 04 04:06:44.208 INFO kablam! 14 | / test!(passing_test_should_never_have_its_output_printed, {
Sep 04 04:06:44.208 INFO kablam! 15 | |     assert_eq!(99, get_some_value());
Sep 04 04:06:44.208 INFO kablam! 16 | | });
Sep 04 04:06:44.208 INFO kablam!    | |___^
Sep 04 04:06:44.208 INFO kablam!    = note: this error originates in a macro outside of the current crate (in Nightly builds, run with -Z external-macro-backtrace for more info)
Sep 04 04:06:44.208 INFO kablam! 
Sep 04 04:06:44.208 INFO kablam! error[E0659]: `test` is ambiguous
Sep 04 04:06:44.209 INFO kablam!   --> tests/should_pass.rs:18:1
Sep 04 04:06:44.209 INFO kablam!    |
Sep 04 04:06:44.209 INFO kablam! 18 | / test!(should_panic, test_may_specify_that_it_should_panic, {
Sep 04 04:06:44.209 INFO kablam! 19 | |     panic!("This test is supposed to fail")
Sep 04 04:06:44.209 INFO kablam! 20 | | });
Sep 04 04:06:44.209 INFO kablam!    | |___^
Sep 04 04:06:44.209 INFO kablam!    |
Sep 04 04:06:44.209 INFO kablam! note: `test` could refer to the name imported here
Sep 04 04:06:44.209 INFO kablam!   --> tests/should_pass.rs:1:1
Sep 04 04:06:44.209 INFO kablam!    |
Sep 04 04:06:44.209 INFO kablam! 1  | #[macro_use]
Sep 04 04:06:44.209 INFO kablam!    | ^^^^^^^^^^^^
Sep 04 04:06:44.209 INFO kablam! note: `test` could also refer to the name defined here
Sep 04 04:06:44.209 INFO kablam!   --> tests/should_pass.rs:18:1
Sep 04 04:06:44.209 INFO kablam!    |
Sep 04 04:06:44.209 INFO kablam! 18 | / test!(should_panic, test_may_specify_that_it_should_panic, {
Sep 04 04:06:44.209 INFO kablam! 19 | |     panic!("This test is supposed to fail")
Sep 04 04:06:44.209 INFO kablam! 20 | | });
Sep 04 04:06:44.209 INFO kablam!    | |___^
Sep 04 04:06:44.209 INFO kablam!    = note: this error originates in a macro outside of the current crate (in Nightly builds, run with -Z external-macro-backtrace for more info)
Sep 04 04:06:44.209 INFO kablam! 
Sep 04 04:06:44.209 INFO kablam! error[E0659]: `test` is ambiguous
Sep 04 04:06:44.209 INFO kablam!   --> tests/should_pass.rs:22:1
Sep 04 04:06:44.209 INFO kablam!    |
Sep 04 04:06:44.209 INFO kablam! 22 | / test!(#[should_panic], test_may_specify_that_it_should_panic_by_using_the_full_attribute, {
Sep 04 04:06:44.209 INFO kablam! 23 | |     panic!("This test also is supposed to fail")
Sep 04 04:06:44.209 INFO kablam! 24 | | });
Sep 04 04:06:44.210 INFO kablam!    | |___^
Sep 04 04:06:44.210 INFO kablam!    |
Sep 04 04:06:44.210 INFO kablam! note: `test` could refer to the name imported here
Sep 04 04:06:44.210 INFO kablam!   --> tests/should_pass.rs:1:1
Sep 04 04:06:44.210 INFO kablam!    |
Sep 04 04:06:44.210 INFO kablam! 1  | #[macro_use]
Sep 04 04:06:44.210 INFO kablam!    | ^^^^^^^^^^^^
Sep 04 04:06:44.210 INFO kablam! note: `test` could also refer to the name defined here
Sep 04 04:06:44.210 INFO kablam!   --> tests/should_pass.rs:22:1
Sep 04 04:06:44.210 INFO kablam!    |
Sep 04 04:06:44.210 INFO kablam! 22 | / test!(#[should_panic], test_may_specify_that_it_should_panic_by_using_the_full_attribute, {
Sep 04 04:06:44.210 INFO kablam! 23 | |     panic!("This test also is supposed to fail")
Sep 04 04:06:44.210 INFO kablam! 24 | | });
Sep 04 04:06:44.210 INFO kablam!    | |___^
Sep 04 04:06:44.210 INFO kablam!    = note: this error originates in a macro outside of the current crate (in Nightly builds, run with -Z external-macro-backtrace for more info)
Sep 04 04:06:44.210 INFO kablam! 
Sep 04 04:06:44.283 INFO kablam! error[E0659]: `test` is ambiguous
Sep 04 04:06:44.283 INFO kablam!   --> tests/should_fail.rs:13:1
Sep 04 04:06:44.283 INFO kablam!    |
Sep 04 04:06:44.284 INFO kablam! 13 | / test!(failing_test_has_log_output_printed_if_log_level_is_high_enough, {
Sep 04 04:06:44.284 INFO kablam! 14 | |     assert_eq!(100, get_some_value());
Sep 04 04:06:44.284 INFO kablam! 15 | | });
Sep 04 04:06:44.284 INFO kablam!    | |___^
Sep 04 04:06:44.284 INFO kablam!    |
Sep 04 04:06:44.284 INFO kablam! note: `test` could refer to the name imported here
Sep 04 04:06:44.284 INFO kablam!   --> tests/should_fail.rs:1:1
Sep 04 04:06:44.284 INFO kablam!    |
Sep 04 04:06:44.284 INFO kablam! 1  | #[macro_use]
Sep 04 04:06:44.284 INFO kablam!    | ^^^^^^^^^^^^
Sep 04 04:06:44.284 INFO kablam! note: `test` could also refer to the name defined here
Sep 04 04:06:44.284 INFO kablam!   --> tests/should_fail.rs:13:1
Sep 04 04:06:44.284 INFO kablam!    |
Sep 04 04:06:44.284 INFO kablam! 13 | / test!(failing_test_has_log_output_printed_if_log_level_is_high_enough, {
Sep 04 04:06:44.284 INFO kablam! 14 | |     assert_eq!(100, get_some_value());
Sep 04 04:06:44.284 INFO kablam! 15 | | });
Sep 04 04:06:44.284 INFO kablam!    | |___^
Sep 04 04:06:44.284 INFO kablam!    = note: this error originates in a macro outside of the current crate (in Nightly builds, run with -Z external-macro-backtrace for more info)
Sep 04 04:06:44.284 INFO kablam! 
Sep 04 04:06:44.361 INFO kablam! error: aborting due to 3 previous errors
Sep 04 04:06:44.361 INFO kablam! 
Sep 04 04:06:44.361 INFO kablam! For more information about this error, try `rustc --explain E0659`.
Sep 04 04:06:44.369 INFO kablam! error: Could not compile `test-logger`.
Sep 04 04:06:44.369 INFO kablam! warning: build failed, waiting for other jobs to finish...
Sep 04 04:06:44.409 INFO kablam! error: aborting due to previous error
Sep 04 04:06:44.409 INFO kablam! 
Sep 04 04:06:44.409 INFO kablam! For more information about this error, try `rustc --explain E0659`.
Sep 04 04:06:44.416 INFO kablam! error: Could not compile `test-logger`.
Sep 04 04:06:44.416 INFO kablam! 
Sep 04 04:06:44.416 INFO kablam! To learn more, run the command again with --verbose.
Sep 04 04:06:44.418 INFO kablam! su: No module specific data is present
Sep 04 04:06:44.807 INFO running `"docker" "rm" "-f" "cc89f5307b07f3a18523ab3543c9021301a9322faf6071f411f71383e3a7c845"`
Sep 04 04:06:44.902 INFO blam! cc89f5307b07f3a18523ab3543c9021301a9322faf6071f411f71383e3a7c845