Dec 01 00:33:00.210 INFO checking cluColor-0.1.5 against try#32252761328f59ccfadb1bafb8148c685bc830b3 for pr-56323 Dec 01 00:33:00.210 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/pr-56323/worker-7/try#32252761328f59ccfadb1bafb8148c685bc830b3:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-7/pr-56323/try#32252761328f59ccfadb1bafb8148c685bc830b3:/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 +32252761328f59ccfadb1bafb8148c685bc830b3-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:00.580 INFO [stdout] 99387148ac67f9d197df3a3ef640030c6156a78071484dcf6aa42fd21f207c01 Dec 01 00:33:00.582 INFO running `"docker" "start" "-a" "99387148ac67f9d197df3a3ef640030c6156a78071484dcf6aa42fd21f207c01"` Dec 01 00:33:02.200 INFO [stderr] usermod: no changes Dec 01 00:33:02.240 INFO [stderr] Checking cluColor v0.1.5 (/source) Dec 01 00:33:06.084 INFO [stderr] warning: unused `std::result::Result` that must be used Dec 01 00:33:06.084 INFO [stderr] --> examples/use_write.rs:15:3 Dec 01 00:33:06.084 INFO [stderr] | Dec 01 00:33:06.084 INFO [stderr] 15 | write_color!(&mut lock_stdio, BrightBlue, "{} {} macro write...", 12345, "str"); Dec 01 00:33:06.084 INFO [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Dec 01 00:33:06.084 INFO [stderr] | Dec 01 00:33:06.084 INFO [stderr] = note: #[warn(unused_must_use)] on by default Dec 01 00:33:06.084 INFO [stderr] = note: this `Result` may be an `Err` variant, which should be handled Dec 01 00:33:06.084 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.084 INFO [stderr] Dec 01 00:33:06.084 INFO [stderr] warning: unused `std::result::Result` that must be used Dec 01 00:33:06.084 INFO [stderr] --> examples/use_write.rs:16:3 Dec 01 00:33:06.085 INFO [stderr] | Dec 01 00:33:06.085 INFO [stderr] 16 | write_color!(lock_stdio, BrightBlue, "{} {} macro write...", 123465, "str"); Dec 01 00:33:06.085 INFO [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Dec 01 00:33:06.085 INFO [stderr] | Dec 01 00:33:06.085 INFO [stderr] = note: this `Result` may be an `Err` variant, which should be handled Dec 01 00:33:06.085 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.085 INFO [stderr] Dec 01 00:33:06.085 INFO [stderr] warning: unused `std::result::Result` that must be used Dec 01 00:33:06.085 INFO [stderr] --> examples/use_write.rs:31:3 Dec 01 00:33:06.085 INFO [stderr] | Dec 01 00:33:06.085 INFO [stderr] 31 | writen_color!(&mut ::std::io::stdout(), BrightBlue, "{} {}", 123, "str"); Dec 01 00:33:06.085 INFO [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Dec 01 00:33:06.085 INFO [stderr] | Dec 01 00:33:06.085 INFO [stderr] = note: this `Result` may be an `Err` variant, which should be handled Dec 01 00:33:06.085 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.085 INFO [stderr] Dec 01 00:33:06.085 INFO [stderr] warning: unused `std::result::Result` that must be used Dec 01 00:33:06.085 INFO [stderr] --> examples/use_write.rs:34:3 Dec 01 00:33:06.085 INFO [stderr] | Dec 01 00:33:06.085 INFO [stderr] 34 | writen_color!(::std::io::stdout(), BrightBlue, "{} {}", 12345, "str"); Dec 01 00:33:06.085 INFO [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Dec 01 00:33:06.085 INFO [stderr] | Dec 01 00:33:06.085 INFO [stderr] = note: this `Result` may be an `Err` variant, which should be handled Dec 01 00:33:06.085 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.085 INFO [stderr] Dec 01 00:33:06.098 INFO [stderr] Finished dev [unoptimized + debuginfo] target(s) in 3.87s Dec 01 00:33:06.099 INFO [stderr] su: No module specific data is present Dec 01 00:33:07.129 INFO running `"docker" "inspect" "99387148ac67f9d197df3a3ef640030c6156a78071484dcf6aa42fd21f207c01"` Dec 01 00:33:07.448 INFO running `"docker" "rm" "-f" "99387148ac67f9d197df3a3ef640030c6156a78071484dcf6aa42fd21f207c01"` Dec 01 00:33:07.797 INFO [stdout] 99387148ac67f9d197df3a3ef640030c6156a78071484dcf6aa42fd21f207c01