Dec 12 06:55:19.661 INFO checking stlog-0.3.2 against master#3a75e80557a103497cffbcab395a2f37061a77ea for pr-56677
Dec 12 06:55:19.661 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/pr-56677/worker-2/master#3a75e80557a103497cffbcab395a2f37061a77ea:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-2/pr-56677/master#3a75e80557a103497cffbcab395a2f37061a77ea:/source:ro,Z" "-v" "/mnt/big/crater/work/local/cargo-home:/cargo-home:ro,Z" "-v" "/mnt/big/crater/work/local/rustup-home:/rustup-home:ro,Z" "-e" "USER_ID=1000" "-e" "SOURCE_DIR=/source" "-e" "USER_ID=1000" "-e" "CMD=cargo +3a75e80557a103497cffbcab395a2f37061a77ea-alt check --frozen --all --all-targets" "-e" "CARGO_TARGET_DIR=/target" "-e" "CARGO_INCREMENTAL=0" "-e" "RUST_BACKTRACE=full" "-e" "RUSTFLAGS=--cap-lints=forbid" "-e" "CARGO_HOME=/cargo-home" "-e" "RUSTUP_HOME=/rustup-home" "-m" "1536M" "--network" "none" "crater"`
Dec 12 06:55:19.895 INFO [stdout] cddf2d9b87494a26c58f9b4ff1b5b6c98b2da416599bf1dfadd4b854555482b3
Dec 12 06:55:19.898 INFO running `"docker" "start" "-a" "cddf2d9b87494a26c58f9b4ff1b5b6c98b2da416599bf1dfadd4b854555482b3"`
Dec 12 06:55:20.378 INFO [stderr] usermod: no changes
Dec 12 06:55:20.506 INFO [stderr]    Compiling stlog-macros v0.1.1
Dec 12 06:55:20.512 INFO [stderr]    Compiling stlog v0.3.2 (/source)
Dec 12 06:55:24.404 INFO [stderr] warning: unused `std::result::Result` that must be used
Dec 12 06:55:24.404 INFO [stderr]   --> examples/local.rs:18:5
Dec 12 06:55:24.404 INFO [stderr]    |
Dec 12 06:55:24.404 INFO [stderr] 18 |     info!(logger, "Hello!");
Dec 12 06:55:24.404 INFO [stderr]    |     ^^^^^^^^^^^^^^^^^^^^^^^^
Dec 12 06:55:24.404 INFO [stderr]    |
Dec 12 06:55:24.404 INFO [stderr]    = note: #[warn(unused_must_use)] on by default
Dec 12 06:55:24.404 INFO [stderr]    = note: this `Result` may be an `Err` variant, which should be handled
Dec 12 06:55:24.404 INFO [stderr]    = note: this error originates in a macro outside of the current crate (in Nightly builds, run with -Z external-macro-backtrace for more info)
Dec 12 06:55:24.404 INFO [stderr] 
Dec 12 06:55:24.404 INFO [stderr] warning: unused `std::result::Result` that must be used
Dec 12 06:55:24.404 INFO [stderr]   --> examples/local.rs:19:5
Dec 12 06:55:24.404 INFO [stderr]    |
Dec 12 06:55:24.404 INFO [stderr] 19 |     error!(logger, "Bye!");
Dec 12 06:55:24.404 INFO [stderr]    |     ^^^^^^^^^^^^^^^^^^^^^^^
Dec 12 06:55:24.404 INFO [stderr]    |
Dec 12 06:55:24.404 INFO [stderr]    = note: this `Result` may be an `Err` variant, which should be handled
Dec 12 06:55:24.404 INFO [stderr]    = note: this error originates in a macro outside of the current crate (in Nightly builds, run with -Z external-macro-backtrace for more info)
Dec 12 06:55:24.404 INFO [stderr] 
Dec 12 06:55:24.423 INFO [stderr]     Finished dev [unoptimized + debuginfo] target(s) in 4.01s
Dec 12 06:55:24.428 INFO [stderr] su: No module specific data is present
Dec 12 06:55:24.930 INFO running `"docker" "inspect" "cddf2d9b87494a26c58f9b4ff1b5b6c98b2da416599bf1dfadd4b854555482b3"`
Dec 12 06:55:25.186 INFO running `"docker" "rm" "-f" "cddf2d9b87494a26c58f9b4ff1b5b6c98b2da416599bf1dfadd4b854555482b3"`
Dec 12 06:55:25.484 INFO [stdout] cddf2d9b87494a26c58f9b4ff1b5b6c98b2da416599bf1dfadd4b854555482b3