Nov 29 03:10:43.121 INFO checking cluColor-0.1.5 against master#0b9f19dff1347e29bf4362ab5a8fab84b43023b5 for pr-56074 Nov 29 03:10:43.121 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/pr-56074/worker-4/master#0b9f19dff1347e29bf4362ab5a8fab84b43023b5:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-4/pr-56074/master#0b9f19dff1347e29bf4362ab5a8fab84b43023b5:/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 +0b9f19dff1347e29bf4362ab5a8fab84b43023b5-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"` Nov 29 03:10:43.549 INFO [stdout] f17e362c375403f0adf8eda81354e3a6757bc6c2eb79384e45071bbbcbfff57d Nov 29 03:10:43.554 INFO running `"docker" "start" "-a" "f17e362c375403f0adf8eda81354e3a6757bc6c2eb79384e45071bbbcbfff57d"` Nov 29 03:10:45.124 INFO [stderr] usermod: no changes Nov 29 03:10:45.188 INFO [stderr] Checking cluColor v0.1.5 (/source) Nov 29 03:10:48.408 INFO [stderr] warning: unused `std::result::Result` that must be used Nov 29 03:10:48.408 INFO [stderr] --> examples/use_write.rs:15:3 Nov 29 03:10:48.408 INFO [stderr] | Nov 29 03:10:48.408 INFO [stderr] 15 | write_color!(&mut lock_stdio, BrightBlue, "{} {} macro write...", 12345, "str"); Nov 29 03:10:48.408 INFO [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Nov 29 03:10:48.408 INFO [stderr] | Nov 29 03:10:48.408 INFO [stderr] = note: #[warn(unused_must_use)] on by default Nov 29 03:10:48.408 INFO [stderr] = note: this `Result` may be an `Err` variant, which should be handled Nov 29 03:10:48.408 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) Nov 29 03:10:48.408 INFO [stderr] Nov 29 03:10:48.408 INFO [stderr] warning: unused `std::result::Result` that must be used Nov 29 03:10:48.408 INFO [stderr] --> examples/use_write.rs:16:3 Nov 29 03:10:48.408 INFO [stderr] | Nov 29 03:10:48.408 INFO [stderr] 16 | write_color!(lock_stdio, BrightBlue, "{} {} macro write...", 123465, "str"); Nov 29 03:10:48.408 INFO [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Nov 29 03:10:48.408 INFO [stderr] | Nov 29 03:10:48.408 INFO [stderr] = note: this `Result` may be an `Err` variant, which should be handled Nov 29 03:10:48.408 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) Nov 29 03:10:48.408 INFO [stderr] Nov 29 03:10:48.409 INFO [stderr] warning: unused `std::result::Result` that must be used Nov 29 03:10:48.409 INFO [stderr] --> examples/use_write.rs:31:3 Nov 29 03:10:48.409 INFO [stderr] | Nov 29 03:10:48.409 INFO [stderr] 31 | writen_color!(&mut ::std::io::stdout(), BrightBlue, "{} {}", 123, "str"); Nov 29 03:10:48.409 INFO [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Nov 29 03:10:48.409 INFO [stderr] | Nov 29 03:10:48.409 INFO [stderr] = note: this `Result` may be an `Err` variant, which should be handled Nov 29 03:10:48.409 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) Nov 29 03:10:48.409 INFO [stderr] Nov 29 03:10:48.409 INFO [stderr] warning: unused `std::result::Result` that must be used Nov 29 03:10:48.409 INFO [stderr] --> examples/use_write.rs:34:3 Nov 29 03:10:48.409 INFO [stderr] | Nov 29 03:10:48.409 INFO [stderr] 34 | writen_color!(::std::io::stdout(), BrightBlue, "{} {}", 12345, "str"); Nov 29 03:10:48.409 INFO [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Nov 29 03:10:48.409 INFO [stderr] | Nov 29 03:10:48.409 INFO [stderr] = note: this `Result` may be an `Err` variant, which should be handled Nov 29 03:10:48.409 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) Nov 29 03:10:48.409 INFO [stderr] Nov 29 03:10:48.604 INFO [stderr] Finished dev [unoptimized + debuginfo] target(s) in 3.44s Nov 29 03:10:48.604 INFO [stderr] su: No module specific data is present Nov 29 03:10:49.188 INFO running `"docker" "inspect" "f17e362c375403f0adf8eda81354e3a6757bc6c2eb79384e45071bbbcbfff57d"` Nov 29 03:10:49.334 INFO running `"docker" "rm" "-f" "f17e362c375403f0adf8eda81354e3a6757bc6c2eb79384e45071bbbcbfff57d"` Nov 29 03:10:49.544 INFO [stdout] f17e362c375403f0adf8eda81354e3a6757bc6c2eb79384e45071bbbcbfff57d