Nov 10 07:20:53.005 INFO checking dbgen-0.1.0 against master#653da4fd006c97625247acd7e076d0782cdc149b for pr-55632 Nov 10 07:20:53.005 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/pr-55632/worker-4/master#653da4fd006c97625247acd7e076d0782cdc149b:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-4/pr-55632/master#653da4fd006c97625247acd7e076d0782cdc149b:/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 +653da4fd006c97625247acd7e076d0782cdc149b-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 10 07:20:53.519 INFO blam! 23807b579878f105c55efebc483c3e500eb85f2133932d21901b0f5ff0ac615a Nov 10 07:20:53.531 INFO running `"docker" "start" "-a" "23807b579878f105c55efebc483c3e500eb85f2133932d21901b0f5ff0ac615a"` Nov 10 07:20:55.431 INFO kablam! usermod: no changes Nov 10 07:20:55.659 INFO kablam! Checking zipf v4.0.1 Nov 10 07:20:56.543 INFO kablam! Checking dbgen v0.1.0 (/source) Nov 10 07:21:02.751 INFO kablam! warning: unused `std::result::Result` that must be used Nov 10 07:21:02.751 INFO kablam! --> src/value.rs:278:21 Nov 10 07:21:02.751 INFO kablam! | Nov 10 07:21:02.751 INFO kablam! 278 | write!(&mut res.bytes, "{}", n); Nov 10 07:21:02.751 INFO kablam! | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Nov 10 07:21:02.751 INFO kablam! | Nov 10 07:21:02.751 INFO kablam! = note: #[warn(unused_must_use)] on by default Nov 10 07:21:02.751 INFO kablam! = note: this `Result` may be an `Err` variant, which should be handled Nov 10 07:21:02.751 INFO kablam! = 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 10 07:21:02.751 INFO kablam! Nov 10 07:21:02.751 INFO kablam! warning: unused `std::result::Result` that must be used Nov 10 07:21:02.751 INFO kablam! --> src/value.rs:291:21 Nov 10 07:21:02.751 INFO kablam! | Nov 10 07:21:02.751 INFO kablam! 291 | write!(&mut res.bytes, "{}", timestamp.format(TIMESTAMP_FORMAT)); Nov 10 07:21:02.751 INFO kablam! | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Nov 10 07:21:02.751 INFO kablam! | Nov 10 07:21:02.751 INFO kablam! = note: this `Result` may be an `Err` variant, which should be handled Nov 10 07:21:02.751 INFO kablam! = 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 10 07:21:02.752 INFO kablam! Nov 10 07:21:02.752 INFO kablam! warning: unused `std::result::Result` that must be used Nov 10 07:21:02.752 INFO kablam! --> src/value.rs:294:21 Nov 10 07:21:02.752 INFO kablam! | Nov 10 07:21:02.752 INFO kablam! 294 | write!(&mut res.bytes, "INTERVAL {} MICROSECOND", interval); Nov 10 07:21:02.752 INFO kablam! | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Nov 10 07:21:02.752 INFO kablam! | Nov 10 07:21:02.752 INFO kablam! = note: this `Result` may be an `Err` variant, which should be handled Nov 10 07:21:02.752 INFO kablam! = 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 10 07:21:02.752 INFO kablam! Nov 10 07:21:02.815 INFO kablam! warning: unused `std::result::Result` that must be used Nov 10 07:21:02.815 INFO kablam! --> src/value.rs:278:21 Nov 10 07:21:02.815 INFO kablam! | Nov 10 07:21:02.815 INFO kablam! 278 | write!(&mut res.bytes, "{}", n); Nov 10 07:21:02.815 INFO kablam! | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Nov 10 07:21:02.815 INFO kablam! | Nov 10 07:21:02.815 INFO kablam! = note: #[warn(unused_must_use)] on by default Nov 10 07:21:02.815 INFO kablam! = note: this `Result` may be an `Err` variant, which should be handled Nov 10 07:21:02.815 INFO kablam! = 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 10 07:21:02.815 INFO kablam! Nov 10 07:21:02.815 INFO kablam! warning: unused `std::result::Result` that must be used Nov 10 07:21:02.815 INFO kablam! --> src/value.rs:291:21 Nov 10 07:21:02.815 INFO kablam! | Nov 10 07:21:02.815 INFO kablam! 291 | write!(&mut res.bytes, "{}", timestamp.format(TIMESTAMP_FORMAT)); Nov 10 07:21:02.815 INFO kablam! | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Nov 10 07:21:02.815 INFO kablam! | Nov 10 07:21:02.815 INFO kablam! = note: this `Result` may be an `Err` variant, which should be handled Nov 10 07:21:02.815 INFO kablam! = 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 10 07:21:02.815 INFO kablam! Nov 10 07:21:02.815 INFO kablam! warning: unused `std::result::Result` that must be used Nov 10 07:21:02.816 INFO kablam! --> src/value.rs:294:21 Nov 10 07:21:02.816 INFO kablam! | Nov 10 07:21:02.816 INFO kablam! 294 | write!(&mut res.bytes, "INTERVAL {} MICROSECOND", interval); Nov 10 07:21:02.816 INFO kablam! | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Nov 10 07:21:02.816 INFO kablam! | Nov 10 07:21:02.816 INFO kablam! = note: this `Result` may be an `Err` variant, which should be handled Nov 10 07:21:02.816 INFO kablam! = 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 10 07:21:02.816 INFO kablam! Nov 10 07:21:07.810 INFO kablam! Finished dev [unoptimized + debuginfo] target(s) in 12.33s Nov 10 07:21:07.810 INFO kablam! su: No module specific data is present Nov 10 07:21:08.436 INFO running `"docker" "rm" "-f" "23807b579878f105c55efebc483c3e500eb85f2133932d21901b0f5ff0ac615a"` Nov 10 07:21:08.554 INFO blam! 23807b579878f105c55efebc483c3e500eb85f2133932d21901b0f5ff0ac615a