Nov 28 15:15:21.090 INFO checking xcp-0.1.1-alpha.2 against try#db42d4dad33013eba11ef37342ad9f614e5652b8 for pr-56074 Nov 28 15:15:21.092 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/pr-56074/worker-2/try#db42d4dad33013eba11ef37342ad9f614e5652b8:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-2/pr-56074/try#db42d4dad33013eba11ef37342ad9f614e5652b8:/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 +db42d4dad33013eba11ef37342ad9f614e5652b8-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 28 15:15:21.338 INFO [stdout] 3c4fa4ad10fc0cf5a0d707cbb5f197a91910054fd92ec48e63a7b42ce75fd409 Nov 28 15:15:21.341 INFO running `"docker" "start" "-a" "3c4fa4ad10fc0cf5a0d707cbb5f197a91910054fd92ec48e63a7b42ce75fd409"` Nov 28 15:15:21.904 INFO [stderr] usermod: no changes Nov 28 15:15:22.179 INFO [stderr] Checking crossbeam-epoch v0.6.1 Nov 28 15:15:22.179 INFO [stderr] Compiling parking_lot_core v0.4.0 Nov 28 15:15:22.192 INFO [stderr] Compiling structopt-derive v0.2.13 Nov 28 15:15:22.192 INFO [stderr] Checking simplelog v0.5.3 Nov 28 15:15:22.192 INFO [stderr] Checking serde v1.0.80 Nov 28 15:15:25.376 INFO [stderr] Checking crossbeam-channel v0.2.6 Nov 28 15:15:28.340 INFO [stderr] Checking parking_lot v0.7.0 Nov 28 15:15:30.696 INFO [stderr] Checking ignore v0.4.4 Nov 28 15:15:33.209 INFO [stderr] Checking console v0.7.0 Nov 28 15:15:40.048 INFO [stderr] Checking indicatif v0.9.0 Nov 28 15:15:42.109 INFO [stderr] Checking structopt v0.2.13 Nov 28 15:15:44.632 INFO [stderr] Checking xcp v0.1.1-alpha.2 (/source) Nov 28 15:15:46.407 INFO [stderr] Checking serde_json v1.0.33 Nov 28 15:15:52.379 INFO [stderr] Checking escargot v0.3.1 Nov 28 15:15:57.876 INFO [stderr] warning: unused `std::result::Result` that must be used Nov 28 15:15:57.877 INFO [stderr] --> tests/lib.rs:51:5 Nov 28 15:15:57.878 INFO [stderr] | Nov 28 15:15:57.878 INFO [stderr] 51 | write!(&file, "{}", text); Nov 28 15:15:57.879 INFO [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^ Nov 28 15:15:57.880 INFO [stderr] | Nov 28 15:15:57.881 INFO [stderr] = note: #[warn(unused_must_use)] on by default Nov 28 15:15:57.881 INFO [stderr] = note: this `Result` may be an `Err` variant, which should be handled Nov 28 15:15:57.882 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 28 15:15:57.883 INFO [stderr] Nov 28 15:15:57.884 INFO [stderr] warning: unused `std::result::Result` that must be used Nov 28 15:15:57.885 INFO [stderr] --> tests/lib.rs:79:5 Nov 28 15:15:57.885 INFO [stderr] | Nov 28 15:15:57.886 INFO [stderr] 79 | write!(fd, "{}", data); Nov 28 15:15:57.887 INFO [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^ Nov 28 15:15:57.887 INFO [stderr] | Nov 28 15:15:57.888 INFO [stderr] = note: this `Result` may be an `Err` variant, which should be handled Nov 28 15:15:57.889 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 28 15:15:57.889 INFO [stderr] Nov 28 15:15:57.890 INFO [stderr] warning: unused `std::result::Result` that must be used Nov 28 15:15:57.891 INFO [stderr] --> tests/lib.rs:82:5 Nov 28 15:15:57.891 INFO [stderr] | Nov 28 15:15:57.892 INFO [stderr] 82 | write!(fd, "{}", data); Nov 28 15:15:57.893 INFO [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^ Nov 28 15:15:57.894 INFO [stderr] | Nov 28 15:15:57.894 INFO [stderr] = note: this `Result` may be an `Err` variant, which should be handled Nov 28 15:15:57.895 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 28 15:15:57.896 INFO [stderr] Nov 28 15:15:57.896 INFO [stderr] warning: unused `std::result::Result` that must be used Nov 28 15:15:57.897 INFO [stderr] --> tests/lib.rs:85:5 Nov 28 15:15:57.898 INFO [stderr] | Nov 28 15:15:57.898 INFO [stderr] 85 | write!(fd, "{}", data); Nov 28 15:15:57.899 INFO [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^ Nov 28 15:15:57.900 INFO [stderr] | Nov 28 15:15:57.901 INFO [stderr] = note: this `Result` may be an `Err` variant, which should be handled Nov 28 15:15:57.901 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 28 15:15:57.902 INFO [stderr] Nov 28 15:15:59.852 INFO [stderr] warning: unused `std::result::Result` that must be used Nov 28 15:15:59.852 INFO [stderr] --> src/os.rs:217:13 Nov 28 15:15:59.852 INFO [stderr] | Nov 28 15:15:59.852 INFO [stderr] 217 | write!(fd, "{}", "test"); Nov 28 15:15:59.852 INFO [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^ Nov 28 15:15:59.852 INFO [stderr] | Nov 28 15:15:59.853 INFO [stderr] = note: #[warn(unused_must_use)] on by default Nov 28 15:15:59.853 INFO [stderr] = note: this `Result` may be an `Err` variant, which should be handled Nov 28 15:15:59.854 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 28 15:15:59.854 INFO [stderr] Nov 28 15:15:59.854 INFO [stderr] warning: unused `std::result::Result` that must be used Nov 28 15:15:59.854 INFO [stderr] --> src/os.rs:233:13 Nov 28 15:15:59.854 INFO [stderr] | Nov 28 15:15:59.854 INFO [stderr] 233 | write!(fd, "{}", data); Nov 28 15:15:59.854 INFO [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^ Nov 28 15:15:59.854 INFO [stderr] | Nov 28 15:15:59.854 INFO [stderr] = note: this `Result` may be an `Err` variant, which should be handled Nov 28 15:15:59.854 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 28 15:15:59.854 INFO [stderr] Nov 28 15:15:59.856 INFO [stderr] warning: unused `std::result::Result` that must be used Nov 28 15:15:59.856 INFO [stderr] --> src/os.rs:265:13 Nov 28 15:15:59.856 INFO [stderr] | Nov 28 15:15:59.856 INFO [stderr] 265 | write!(fd, "{}", data); Nov 28 15:15:59.856 INFO [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^ Nov 28 15:15:59.856 INFO [stderr] | Nov 28 15:15:59.856 INFO [stderr] = note: this `Result` may be an `Err` variant, which should be handled Nov 28 15:15:59.856 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 28 15:15:59.856 INFO [stderr] Nov 28 15:15:59.856 INFO [stderr] warning: unused `std::result::Result` that must be used Nov 28 15:15:59.856 INFO [stderr] --> src/os.rs:308:13 Nov 28 15:15:59.856 INFO [stderr] | Nov 28 15:15:59.856 INFO [stderr] 308 | write!(fd, "{}", data); Nov 28 15:15:59.856 INFO [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^ Nov 28 15:15:59.856 INFO [stderr] | Nov 28 15:15:59.856 INFO [stderr] = note: this `Result` may be an `Err` variant, which should be handled Nov 28 15:15:59.856 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 28 15:15:59.856 INFO [stderr] Nov 28 15:15:59.856 INFO [stderr] warning: unused `std::result::Result` that must be used Nov 28 15:15:59.856 INFO [stderr] --> src/os.rs:344:13 Nov 28 15:15:59.856 INFO [stderr] | Nov 28 15:15:59.856 INFO [stderr] 344 | write!(fd, "{}", data); Nov 28 15:15:59.856 INFO [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^ Nov 28 15:15:59.856 INFO [stderr] | Nov 28 15:15:59.856 INFO [stderr] = note: this `Result` may be an `Err` variant, which should be handled Nov 28 15:15:59.856 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 28 15:15:59.856 INFO [stderr] Nov 28 15:15:59.859 INFO [stderr] warning: unused `std::result::Result` that must be used Nov 28 15:15:59.859 INFO [stderr] --> src/os.rs:347:13 Nov 28 15:15:59.859 INFO [stderr] | Nov 28 15:15:59.859 INFO [stderr] 347 | write!(fd, "{}", data); Nov 28 15:15:59.859 INFO [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^ Nov 28 15:15:59.859 INFO [stderr] | Nov 28 15:15:59.859 INFO [stderr] = note: this `Result` may be an `Err` variant, which should be handled Nov 28 15:15:59.859 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 28 15:15:59.859 INFO [stderr] Nov 28 15:15:59.859 INFO [stderr] warning: unused `std::result::Result` that must be used Nov 28 15:15:59.859 INFO [stderr] --> src/os.rs:350:13 Nov 28 15:15:59.859 INFO [stderr] | Nov 28 15:15:59.859 INFO [stderr] 350 | write!(fd, "{}", data); Nov 28 15:15:59.859 INFO [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^ Nov 28 15:15:59.859 INFO [stderr] | Nov 28 15:15:59.859 INFO [stderr] = note: this `Result` may be an `Err` variant, which should be handled Nov 28 15:15:59.859 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 28 15:15:59.859 INFO [stderr] Nov 28 15:15:59.885 INFO [stderr] Finished dev [unoptimized + debuginfo] target(s) in 37.95s Nov 28 15:15:59.897 INFO [stderr] su: No module specific data is present Nov 28 15:16:00.238 INFO running `"docker" "inspect" "3c4fa4ad10fc0cf5a0d707cbb5f197a91910054fd92ec48e63a7b42ce75fd409"` Nov 28 15:16:00.391 INFO running `"docker" "rm" "-f" "3c4fa4ad10fc0cf5a0d707cbb5f197a91910054fd92ec48e63a7b42ce75fd409"` Nov 28 15:16:00.541 INFO [stdout] 3c4fa4ad10fc0cf5a0d707cbb5f197a91910054fd92ec48e63a7b42ce75fd409