Dec 01 00:33:00.749 INFO checking cluColor-0.1.5 against master#a49316ddc99d9d595193557fc899f6c52e4d9af9 for pr-56323 Dec 01 00:33:00.750 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/pr-56323/worker-0/master#a49316ddc99d9d595193557fc899f6c52e4d9af9:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-0/pr-56323/master#a49316ddc99d9d595193557fc899f6c52e4d9af9:/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 +a49316ddc99d9d595193557fc899f6c52e4d9af9-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 01 00:33:01.209 INFO [stdout] 795dcad4a748c4e4f71f9b3fcca3f678c868b3837e0f34be18116981db6a2bb5 Dec 01 00:33:01.213 INFO running `"docker" "start" "-a" "795dcad4a748c4e4f71f9b3fcca3f678c868b3837e0f34be18116981db6a2bb5"` Dec 01 00:33:02.800 INFO [stderr] usermod: no changes Dec 01 00:33:02.885 INFO [stderr] Checking cluColor v0.1.5 (/source) Dec 01 00:33:06.500 INFO [stderr] warning: unused `std::result::Result` that must be used Dec 01 00:33:06.500 INFO [stderr] --> examples/use_write.rs:15:3 Dec 01 00:33:06.500 INFO [stderr] | Dec 01 00:33:06.500 INFO [stderr] 15 | write_color!(&mut lock_stdio, BrightBlue, "{} {} macro write...", 12345, "str"); Dec 01 00:33:06.500 INFO [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Dec 01 00:33:06.500 INFO [stderr] | Dec 01 00:33:06.500 INFO [stderr] = note: #[warn(unused_must_use)] on by default Dec 01 00:33:06.500 INFO [stderr] = note: this `Result` may be an `Err` variant, which should be handled Dec 01 00:33:06.500 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 01 00:33:06.500 INFO [stderr] Dec 01 00:33:06.500 INFO [stderr] warning: unused `std::result::Result` that must be used Dec 01 00:33:06.500 INFO [stderr] --> examples/use_write.rs:16:3 Dec 01 00:33:06.500 INFO [stderr] | Dec 01 00:33:06.500 INFO [stderr] 16 | write_color!(lock_stdio, BrightBlue, "{} {} macro write...", 123465, "str"); Dec 01 00:33:06.500 INFO [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Dec 01 00:33:06.500 INFO [stderr] | Dec 01 00:33:06.501 INFO [stderr] = note: this `Result` may be an `Err` variant, which should be handled Dec 01 00:33:06.501 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 01 00:33:06.501 INFO [stderr] Dec 01 00:33:06.501 INFO [stderr] warning: unused `std::result::Result` that must be used Dec 01 00:33:06.501 INFO [stderr] --> examples/use_write.rs:31:3 Dec 01 00:33:06.501 INFO [stderr] | Dec 01 00:33:06.501 INFO [stderr] 31 | writen_color!(&mut ::std::io::stdout(), BrightBlue, "{} {}", 123, "str"); Dec 01 00:33:06.501 INFO [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Dec 01 00:33:06.501 INFO [stderr] | Dec 01 00:33:06.501 INFO [stderr] = note: this `Result` may be an `Err` variant, which should be handled Dec 01 00:33:06.501 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 01 00:33:06.501 INFO [stderr] Dec 01 00:33:06.501 INFO [stderr] warning: unused `std::result::Result` that must be used Dec 01 00:33:06.501 INFO [stderr] --> examples/use_write.rs:34:3 Dec 01 00:33:06.501 INFO [stderr] | Dec 01 00:33:06.501 INFO [stderr] 34 | writen_color!(::std::io::stdout(), BrightBlue, "{} {}", 12345, "str"); Dec 01 00:33:06.501 INFO [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Dec 01 00:33:06.501 INFO [stderr] | Dec 01 00:33:06.501 INFO [stderr] = note: this `Result` may be an `Err` variant, which should be handled Dec 01 00:33:06.501 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 01 00:33:06.501 INFO [stderr] Dec 01 00:33:06.564 INFO [stderr] Finished dev [unoptimized + debuginfo] target(s) in 3.72s Dec 01 00:33:06.564 INFO [stderr] su: No module specific data is present Dec 01 00:33:07.226 INFO running `"docker" "inspect" "795dcad4a748c4e4f71f9b3fcca3f678c868b3837e0f34be18116981db6a2bb5"` Dec 01 00:33:07.520 INFO running `"docker" "rm" "-f" "795dcad4a748c4e4f71f9b3fcca3f678c868b3837e0f34be18116981db6a2bb5"` Dec 01 00:33:07.875 INFO [stdout] 795dcad4a748c4e4f71f9b3fcca3f678c868b3837e0f34be18116981db6a2bb5