Dec 04 13:06:10.172 INFO checking nojima/qurl against try#1df97983eb2057dc6a8f7eb364e263b51ae23230 for pr-56481 Dec 04 13:06:10.172 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/pr-56481/worker-2/try#1df97983eb2057dc6a8f7eb364e263b51ae23230:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-2/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 13:06:10.333 INFO [stdout] d559375ffa0968693a56a4ec4d8cb185e2cebb33c70c44a5c1ccda3a4fd3795b Dec 04 13:06:10.335 INFO running `"docker" "start" "-a" "d559375ffa0968693a56a4ec4d8cb185e2cebb33c70c44a5c1ccda3a4fd3795b"` Dec 04 13:06:10.697 INFO [stderr] usermod: no changes Dec 04 13:06:10.877 INFO [stderr] Checking tokio-reactor v0.1.6 Dec 04 13:06:12.011 INFO [stderr] Checking tokio-tcp v0.1.2 Dec 04 13:06:12.011 INFO [stderr] Checking tokio-uds v0.2.3 Dec 04 13:06:12.011 INFO [stderr] Checking tokio-udp v0.1.2 Dec 04 13:06:14.327 INFO [stderr] Checking tokio v0.1.11 Dec 04 13:06:15.843 INFO [stderr] Checking hyper v0.12.13 Dec 04 13:06:20.487 INFO [stderr] Checking qurl v0.1.0 (/source) Dec 04 13:06:22.593 INFO [stderr] warning: unused `std::result::Result` that must be used Dec 04 13:06:22.593 INFO [stderr] --> src/yaml_to_json.rs:71:13 Dec 04 13:06:22.593 INFO [stderr] | Dec 04 13:06:22.593 INFO [stderr] 71 | write!(out, "{}", real); Dec 04 13:06:22.593 INFO [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^ Dec 04 13:06:22.593 INFO [stderr] | Dec 04 13:06:22.593 INFO [stderr] = note: #[warn(unused_must_use)] on by default Dec 04 13:06:22.593 INFO [stderr] = note: this `Result` may be an `Err` variant, which should be handled Dec 04 13:06:22.593 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 13:06:22.593 INFO [stderr] Dec 04 13:06:22.593 INFO [stderr] warning: unused `std::result::Result` that must be used Dec 04 13:06:22.593 INFO [stderr] --> src/yaml_to_json.rs:74:13 Dec 04 13:06:22.593 INFO [stderr] | Dec 04 13:06:22.593 INFO [stderr] 74 | write!(out, "{}", integer); Dec 04 13:06:22.593 INFO [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^ Dec 04 13:06:22.593 INFO [stderr] | Dec 04 13:06:22.593 INFO [stderr] = note: this `Result` may be an `Err` variant, which should be handled Dec 04 13:06:22.593 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 13:06:22.593 INFO [stderr] Dec 04 13:06:22.593 INFO [stderr] warning: unused `std::result::Result` that must be used Dec 04 13:06:22.593 INFO [stderr] --> src/yaml_to_json.rs:80:13 Dec 04 13:06:22.593 INFO [stderr] | Dec 04 13:06:22.593 INFO [stderr] 80 | write!(out, "{}", boolean); Dec 04 13:06:22.593 INFO [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^ Dec 04 13:06:22.593 INFO [stderr] | Dec 04 13:06:22.593 INFO [stderr] = note: this `Result` may be an `Err` variant, which should be handled Dec 04 13:06:22.593 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 13:06:22.593 INFO [stderr] Dec 04 13:06:22.593 INFO [stderr] warning: unused `std::result::Result` that must be used Dec 04 13:06:22.593 INFO [stderr] --> src/yaml_to_json.rs:83:13 Dec 04 13:06:22.593 INFO [stderr] | Dec 04 13:06:22.593 INFO [stderr] 83 | write!(out, "["); Dec 04 13:06:22.593 INFO [stderr] | ^^^^^^^^^^^^^^^^^ Dec 04 13:06:22.593 INFO [stderr] | Dec 04 13:06:22.593 INFO [stderr] = note: this `Result` may be an `Err` variant, which should be handled Dec 04 13:06:22.593 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 13:06:22.593 INFO [stderr] Dec 04 13:06:22.593 INFO [stderr] warning: unused `std::result::Result` that must be used Dec 04 13:06:22.593 INFO [stderr] --> src/yaml_to_json.rs:90:21 Dec 04 13:06:22.593 INFO [stderr] | Dec 04 13:06:22.593 INFO [stderr] 90 | write!(out, ","); Dec 04 13:06:22.593 INFO [stderr] | ^^^^^^^^^^^^^^^^^ Dec 04 13:06:22.594 INFO [stderr] | Dec 04 13:06:22.594 INFO [stderr] = note: this `Result` may be an `Err` variant, which should be handled Dec 04 13:06:22.594 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 13:06:22.594 INFO [stderr] Dec 04 13:06:22.594 INFO [stderr] warning: unused `std::result::Result` that must be used Dec 04 13:06:22.594 INFO [stderr] --> src/yaml_to_json.rs:95:13 Dec 04 13:06:22.594 INFO [stderr] | Dec 04 13:06:22.594 INFO [stderr] 95 | write!(out, "]"); Dec 04 13:06:22.594 INFO [stderr] | ^^^^^^^^^^^^^^^^^ Dec 04 13:06:22.594 INFO [stderr] | Dec 04 13:06:22.594 INFO [stderr] = note: this `Result` may be an `Err` variant, which should be handled Dec 04 13:06:22.594 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 13:06:22.594 INFO [stderr] Dec 04 13:06:22.594 INFO [stderr] warning: unused `std::result::Result` that must be used Dec 04 13:06:22.594 INFO [stderr] --> src/yaml_to_json.rs:98:13 Dec 04 13:06:22.594 INFO [stderr] | Dec 04 13:06:22.594 INFO [stderr] 98 | write!(out, "{{"); Dec 04 13:06:22.594 INFO [stderr] | ^^^^^^^^^^^^^^^^^^ Dec 04 13:06:22.594 INFO [stderr] | Dec 04 13:06:22.594 INFO [stderr] = note: this `Result` may be an `Err` variant, which should be handled Dec 04 13:06:22.594 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 13:06:22.594 INFO [stderr] Dec 04 13:06:22.594 INFO [stderr] warning: unused `std::result::Result` that must be used Dec 04 13:06:22.594 INFO [stderr] --> src/yaml_to_json.rs:105:21 Dec 04 13:06:22.594 INFO [stderr] | Dec 04 13:06:22.594 INFO [stderr] 105 | write!(out, ","); Dec 04 13:06:22.594 INFO [stderr] | ^^^^^^^^^^^^^^^^^ Dec 04 13:06:22.594 INFO [stderr] | Dec 04 13:06:22.594 INFO [stderr] = note: this `Result` may be an `Err` variant, which should be handled Dec 04 13:06:22.594 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 13:06:22.594 INFO [stderr] Dec 04 13:06:22.594 INFO [stderr] warning: unused `std::result::Result` that must be used Dec 04 13:06:22.594 INFO [stderr] --> src/yaml_to_json.rs:109:21 Dec 04 13:06:22.594 INFO [stderr] | Dec 04 13:06:22.594 INFO [stderr] 109 | write!(out, ":"); Dec 04 13:06:22.594 INFO [stderr] | ^^^^^^^^^^^^^^^^^ Dec 04 13:06:22.594 INFO [stderr] | Dec 04 13:06:22.594 INFO [stderr] = note: this `Result` may be an `Err` variant, which should be handled Dec 04 13:06:22.594 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 13:06:22.594 INFO [stderr] Dec 04 13:06:22.594 INFO [stderr] warning: unused `std::result::Result` that must be used Dec 04 13:06:22.594 INFO [stderr] --> src/yaml_to_json.rs:115:13 Dec 04 13:06:22.594 INFO [stderr] | Dec 04 13:06:22.594 INFO [stderr] 115 | write!(out, "}}"); Dec 04 13:06:22.594 INFO [stderr] | ^^^^^^^^^^^^^^^^^^ Dec 04 13:06:22.594 INFO [stderr] | Dec 04 13:06:22.594 INFO [stderr] = note: this `Result` may be an `Err` variant, which should be handled Dec 04 13:06:22.594 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 13:06:22.594 INFO [stderr] Dec 04 13:06:22.594 INFO [stderr] warning: unused `std::result::Result` that must be used Dec 04 13:06:22.594 INFO [stderr] --> src/yaml_to_json.rs:118:13 Dec 04 13:06:22.594 INFO [stderr] | Dec 04 13:06:22.594 INFO [stderr] 118 | write!(out, "null"); Dec 04 13:06:22.594 INFO [stderr] | ^^^^^^^^^^^^^^^^^^^^ Dec 04 13:06:22.594 INFO [stderr] | Dec 04 13:06:22.594 INFO [stderr] = note: this `Result` may be an `Err` variant, which should be handled Dec 04 13:06:22.594 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 13:06:22.594 INFO [stderr] Dec 04 13:06:22.631 INFO [stderr] warning: unused `std::result::Result` that must be used Dec 04 13:06:22.631 INFO [stderr] --> src/yaml_to_json.rs:71:13 Dec 04 13:06:22.631 INFO [stderr] | Dec 04 13:06:22.631 INFO [stderr] 71 | write!(out, "{}", real); Dec 04 13:06:22.631 INFO [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^ Dec 04 13:06:22.631 INFO [stderr] | Dec 04 13:06:22.631 INFO [stderr] = note: #[warn(unused_must_use)] on by default Dec 04 13:06:22.631 INFO [stderr] = note: this `Result` may be an `Err` variant, which should be handled Dec 04 13:06:22.631 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 13:06:22.631 INFO [stderr] Dec 04 13:06:22.631 INFO [stderr] warning: unused `std::result::Result` that must be used Dec 04 13:06:22.631 INFO [stderr] --> src/yaml_to_json.rs:74:13 Dec 04 13:06:22.631 INFO [stderr] | Dec 04 13:06:22.631 INFO [stderr] 74 | write!(out, "{}", integer); Dec 04 13:06:22.631 INFO [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^ Dec 04 13:06:22.631 INFO [stderr] | Dec 04 13:06:22.631 INFO [stderr] = note: this `Result` may be an `Err` variant, which should be handled Dec 04 13:06:22.631 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 13:06:22.631 INFO [stderr] Dec 04 13:06:22.631 INFO [stderr] warning: unused `std::result::Result` that must be used Dec 04 13:06:22.631 INFO [stderr] --> src/yaml_to_json.rs:80:13 Dec 04 13:06:22.631 INFO [stderr] | Dec 04 13:06:22.631 INFO [stderr] 80 | write!(out, "{}", boolean); Dec 04 13:06:22.631 INFO [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^ Dec 04 13:06:22.631 INFO [stderr] | Dec 04 13:06:22.631 INFO [stderr] = note: this `Result` may be an `Err` variant, which should be handled Dec 04 13:06:22.631 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 13:06:22.631 INFO [stderr] Dec 04 13:06:22.631 INFO [stderr] warning: unused `std::result::Result` that must be used Dec 04 13:06:22.631 INFO [stderr] --> src/yaml_to_json.rs:83:13 Dec 04 13:06:22.631 INFO [stderr] | Dec 04 13:06:22.631 INFO [stderr] 83 | write!(out, "["); Dec 04 13:06:22.632 INFO [stderr] | ^^^^^^^^^^^^^^^^^ Dec 04 13:06:22.632 INFO [stderr] | Dec 04 13:06:22.632 INFO [stderr] = note: this `Result` may be an `Err` variant, which should be handled Dec 04 13:06:22.632 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 13:06:22.632 INFO [stderr] Dec 04 13:06:22.632 INFO [stderr] warning: unused `std::result::Result` that must be used Dec 04 13:06:22.632 INFO [stderr] --> src/yaml_to_json.rs:90:21 Dec 04 13:06:22.632 INFO [stderr] | Dec 04 13:06:22.632 INFO [stderr] 90 | write!(out, ","); Dec 04 13:06:22.632 INFO [stderr] | ^^^^^^^^^^^^^^^^^ Dec 04 13:06:22.632 INFO [stderr] | Dec 04 13:06:22.632 INFO [stderr] = note: this `Result` may be an `Err` variant, which should be handled Dec 04 13:06:22.632 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 13:06:22.632 INFO [stderr] Dec 04 13:06:22.632 INFO [stderr] warning: unused `std::result::Result` that must be used Dec 04 13:06:22.632 INFO [stderr] --> src/yaml_to_json.rs:95:13 Dec 04 13:06:22.632 INFO [stderr] | Dec 04 13:06:22.632 INFO [stderr] 95 | write!(out, "]"); Dec 04 13:06:22.632 INFO [stderr] | ^^^^^^^^^^^^^^^^^ Dec 04 13:06:22.632 INFO [stderr] | Dec 04 13:06:22.632 INFO [stderr] = note: this `Result` may be an `Err` variant, which should be handled Dec 04 13:06:22.632 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 13:06:22.632 INFO [stderr] Dec 04 13:06:22.632 INFO [stderr] warning: unused `std::result::Result` that must be used Dec 04 13:06:22.632 INFO [stderr] --> src/yaml_to_json.rs:98:13 Dec 04 13:06:22.632 INFO [stderr] | Dec 04 13:06:22.632 INFO [stderr] 98 | write!(out, "{{"); Dec 04 13:06:22.632 INFO [stderr] | ^^^^^^^^^^^^^^^^^^ Dec 04 13:06:22.632 INFO [stderr] | Dec 04 13:06:22.632 INFO [stderr] = note: this `Result` may be an `Err` variant, which should be handled Dec 04 13:06:22.632 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 13:06:22.632 INFO [stderr] Dec 04 13:06:22.632 INFO [stderr] warning: unused `std::result::Result` that must be used Dec 04 13:06:22.632 INFO [stderr] --> src/yaml_to_json.rs:105:21 Dec 04 13:06:22.632 INFO [stderr] | Dec 04 13:06:22.632 INFO [stderr] 105 | write!(out, ","); Dec 04 13:06:22.632 INFO [stderr] | ^^^^^^^^^^^^^^^^^ Dec 04 13:06:22.632 INFO [stderr] | Dec 04 13:06:22.632 INFO [stderr] = note: this `Result` may be an `Err` variant, which should be handled Dec 04 13:06:22.632 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 13:06:22.632 INFO [stderr] Dec 04 13:06:22.632 INFO [stderr] warning: unused `std::result::Result` that must be used Dec 04 13:06:22.632 INFO [stderr] --> src/yaml_to_json.rs:109:21 Dec 04 13:06:22.632 INFO [stderr] | Dec 04 13:06:22.632 INFO [stderr] 109 | write!(out, ":"); Dec 04 13:06:22.632 INFO [stderr] | ^^^^^^^^^^^^^^^^^ Dec 04 13:06:22.632 INFO [stderr] | Dec 04 13:06:22.632 INFO [stderr] = note: this `Result` may be an `Err` variant, which should be handled Dec 04 13:06:22.632 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 13:06:22.632 INFO [stderr] Dec 04 13:06:22.632 INFO [stderr] warning: unused `std::result::Result` that must be used Dec 04 13:06:22.632 INFO [stderr] --> src/yaml_to_json.rs:115:13 Dec 04 13:06:22.632 INFO [stderr] | Dec 04 13:06:22.632 INFO [stderr] 115 | write!(out, "}}"); Dec 04 13:06:22.632 INFO [stderr] | ^^^^^^^^^^^^^^^^^^ Dec 04 13:06:22.632 INFO [stderr] | Dec 04 13:06:22.632 INFO [stderr] = note: this `Result` may be an `Err` variant, which should be handled Dec 04 13:06:22.632 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 13:06:22.632 INFO [stderr] Dec 04 13:06:22.632 INFO [stderr] warning: unused `std::result::Result` that must be used Dec 04 13:06:22.632 INFO [stderr] --> src/yaml_to_json.rs:118:13 Dec 04 13:06:22.632 INFO [stderr] | Dec 04 13:06:22.632 INFO [stderr] 118 | write!(out, "null"); Dec 04 13:06:22.632 INFO [stderr] | ^^^^^^^^^^^^^^^^^^^^ Dec 04 13:06:22.632 INFO [stderr] | Dec 04 13:06:22.632 INFO [stderr] = note: this `Result` may be an `Err` variant, which should be handled Dec 04 13:06:22.632 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 13:06:22.632 INFO [stderr] Dec 04 13:06:22.679 INFO [stderr] Finished dev [unoptimized + debuginfo] target(s) in 11.95s Dec 04 13:06:22.703 INFO [stderr] su: No module specific data is present Dec 04 13:06:23.657 INFO running `"docker" "inspect" "d559375ffa0968693a56a4ec4d8cb185e2cebb33c70c44a5c1ccda3a4fd3795b"` Dec 04 13:06:23.849 INFO running `"docker" "rm" "-f" "d559375ffa0968693a56a4ec4d8cb185e2cebb33c70c44a5c1ccda3a4fd3795b"` Dec 04 13:06:24.069 INFO [stdout] d559375ffa0968693a56a4ec4d8cb185e2cebb33c70c44a5c1ccda3a4fd3795b