Dec 04 22:42:14.858 INFO checking ametisf/crop against try#1df97983eb2057dc6a8f7eb364e263b51ae23230 for pr-56481
Dec 04 22:42:14.858 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/pr-56481/worker-7/try#1df97983eb2057dc6a8f7eb364e263b51ae23230:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-7/pr-56481/try#1df97983eb2057dc6a8f7eb364e263b51ae23230:/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 +1df97983eb2057dc6a8f7eb364e263b51ae23230-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 04 22:42:15.339 INFO [stdout] a94df694e2e9810549b987fe4140467659c6165774a46e5dee3d3ce9d12e0942
Dec 04 22:42:15.344 INFO running `"docker" "start" "-a" "a94df694e2e9810549b987fe4140467659c6165774a46e5dee3d3ce9d12e0942"`
Dec 04 22:42:16.743 INFO [stderr] usermod: no changes
Dec 04 22:42:16.803 INFO [stderr]     Checking crop v0.1.0 (/source)
Dec 04 22:42:17.395 INFO [stderr] warning: unused `std::result::Result` that must be used
Dec 04 22:42:17.396 INFO [stderr]   --> src/main.rs:14:13
Dec 04 22:42:17.396 INFO [stderr]    |
Dec 04 22:42:17.396 INFO [stderr] 14 |             writeln!(stdout, "{}…", &line[0..column]);
Dec 04 22:42:17.396 INFO [stderr]    |             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Dec 04 22:42:17.397 INFO [stderr]    |
Dec 04 22:42:17.397 INFO [stderr]    = note: #[warn(unused_must_use)] on by default
Dec 04 22:42:17.397 INFO [stderr]    = note: this `Result` may be an `Err` variant, which should be handled
Dec 04 22:42:17.397 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 04 22:42:17.397 INFO [stderr] 
Dec 04 22:42:17.397 INFO [stderr] warning: unused `std::result::Result` that must be used
Dec 04 22:42:17.397 INFO [stderr]   --> src/main.rs:16:13
Dec 04 22:42:17.397 INFO [stderr]    |
Dec 04 22:42:17.397 INFO [stderr] 16 |             writeln!(stdout, "{}", &line);
Dec 04 22:42:17.397 INFO [stderr]    |             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Dec 04 22:42:17.397 INFO [stderr]    |
Dec 04 22:42:17.397 INFO [stderr]    = note: this `Result` may be an `Err` variant, which should be handled
Dec 04 22:42:17.397 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 04 22:42:17.397 INFO [stderr] 
Dec 04 22:42:17.553 INFO [stderr] warning: unused `std::result::Result` that must be used
Dec 04 22:42:17.553 INFO [stderr]   --> src/main.rs:14:13
Dec 04 22:42:17.554 INFO [stderr]    |
Dec 04 22:42:17.554 INFO [stderr] 14 |             writeln!(stdout, "{}…", &line[0..column]);
Dec 04 22:42:17.554 INFO [stderr]    |             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Dec 04 22:42:17.554 INFO [stderr]    |
Dec 04 22:42:17.554 INFO [stderr]    = note: #[warn(unused_must_use)] on by default
Dec 04 22:42:17.554 INFO [stderr]    = note: this `Result` may be an `Err` variant, which should be handled
Dec 04 22:42:17.554 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 04 22:42:17.554 INFO [stderr] 
Dec 04 22:42:17.554 INFO [stderr] warning: unused `std::result::Result` that must be used
Dec 04 22:42:17.554 INFO [stderr]   --> src/main.rs:16:13
Dec 04 22:42:17.554 INFO [stderr]    |
Dec 04 22:42:17.554 INFO [stderr] 16 |             writeln!(stdout, "{}", &line);
Dec 04 22:42:17.554 INFO [stderr]    |             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Dec 04 22:42:17.554 INFO [stderr]    |
Dec 04 22:42:17.554 INFO [stderr]    = note: this `Result` may be an `Err` variant, which should be handled
Dec 04 22:42:17.554 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 04 22:42:17.554 INFO [stderr] 
Dec 04 22:42:17.599 INFO [stderr]     Finished dev [unoptimized + debuginfo] target(s) in 0.83s
Dec 04 22:42:17.601 INFO [stderr] su: No module specific data is present
Dec 04 22:42:18.201 INFO running `"docker" "inspect" "a94df694e2e9810549b987fe4140467659c6165774a46e5dee3d3ce9d12e0942"`
Dec 04 22:42:18.448 INFO running `"docker" "rm" "-f" "a94df694e2e9810549b987fe4140467659c6165774a46e5dee3d3ce9d12e0942"`
Dec 04 22:42:18.655 INFO [stdout] a94df694e2e9810549b987fe4140467659c6165774a46e5dee3d3ce9d12e0942