Nov 29 21:15:20.468 INFO checking nojima/qurl against master#a49316ddc99d9d595193557fc899f6c52e4d9af9 for pr-56323
Nov 29 21:15:20.468 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/pr-56323/worker-7/master#a49316ddc99d9d595193557fc899f6c52e4d9af9:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-7/pr-56323/master#a49316ddc99d9d595193557fc899f6c52e4d9af9:/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 +a49316ddc99d9d595193557fc899f6c52e4d9af9-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 21:15:20.770 INFO [stdout] 0e54b28254557da6c1d9681fd576b49b2a234f51e035c57ae7454ddbef5d4e7e
Nov 29 21:15:20.773 INFO running `"docker" "start" "-a" "0e54b28254557da6c1d9681fd576b49b2a234f51e035c57ae7454ddbef5d4e7e"`
Nov 29 21:15:21.276 INFO [stderr] usermod: no changes
Nov 29 21:15:21.456 INFO [stderr]     Checking qurl v0.1.0 (/source)
Nov 29 21:15:24.265 INFO [stderr] warning: unused `std::result::Result` that must be used
Nov 29 21:15:24.265 INFO [stderr]   --> src/yaml_to_json.rs:71:13
Nov 29 21:15:24.265 INFO [stderr]    |
Nov 29 21:15:24.265 INFO [stderr] 71 |             write!(out, "{}", real);
Nov 29 21:15:24.265 INFO [stderr]    |             ^^^^^^^^^^^^^^^^^^^^^^^^
Nov 29 21:15:24.265 INFO [stderr]    |
Nov 29 21:15:24.265 INFO [stderr]    = note: #[warn(unused_must_use)] on by default
Nov 29 21:15:24.265 INFO [stderr]    = note: this `Result` may be an `Err` variant, which should be handled
Nov 29 21:15:24.265 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 21:15:24.265 INFO [stderr] 
Nov 29 21:15:24.265 INFO [stderr] warning: unused `std::result::Result` that must be used
Nov 29 21:15:24.265 INFO [stderr]   --> src/yaml_to_json.rs:74:13
Nov 29 21:15:24.265 INFO [stderr]    |
Nov 29 21:15:24.265 INFO [stderr] 74 |             write!(out, "{}", integer);
Nov 29 21:15:24.265 INFO [stderr]    |             ^^^^^^^^^^^^^^^^^^^^^^^^^^^
Nov 29 21:15:24.265 INFO [stderr]    |
Nov 29 21:15:24.265 INFO [stderr]    = note: this `Result` may be an `Err` variant, which should be handled
Nov 29 21:15:24.265 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 21:15:24.265 INFO [stderr] 
Nov 29 21:15:24.265 INFO [stderr] warning: unused `std::result::Result` that must be used
Nov 29 21:15:24.265 INFO [stderr]   --> src/yaml_to_json.rs:80:13
Nov 29 21:15:24.265 INFO [stderr]    |
Nov 29 21:15:24.265 INFO [stderr] 80 |             write!(out, "{}", boolean);
Nov 29 21:15:24.265 INFO [stderr]    |             ^^^^^^^^^^^^^^^^^^^^^^^^^^^
Nov 29 21:15:24.265 INFO [stderr]    |
Nov 29 21:15:24.265 INFO [stderr]    = note: this `Result` may be an `Err` variant, which should be handled
Nov 29 21:15:24.265 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 21:15:24.265 INFO [stderr] 
Nov 29 21:15:24.265 INFO [stderr] warning: unused `std::result::Result` that must be used
Nov 29 21:15:24.265 INFO [stderr]   --> src/yaml_to_json.rs:83:13
Nov 29 21:15:24.265 INFO [stderr]    |
Nov 29 21:15:24.265 INFO [stderr] 83 |             write!(out, "[");
Nov 29 21:15:24.265 INFO [stderr]    |             ^^^^^^^^^^^^^^^^^
Nov 29 21:15:24.265 INFO [stderr]    |
Nov 29 21:15:24.265 INFO [stderr]    = note: this `Result` may be an `Err` variant, which should be handled
Nov 29 21:15:24.265 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 21:15:24.265 INFO [stderr] 
Nov 29 21:15:24.265 INFO [stderr] warning: unused `std::result::Result` that must be used
Nov 29 21:15:24.265 INFO [stderr]   --> src/yaml_to_json.rs:90:21
Nov 29 21:15:24.265 INFO [stderr]    |
Nov 29 21:15:24.265 INFO [stderr] 90 |                     write!(out, ",");
Nov 29 21:15:24.265 INFO [stderr]    |                     ^^^^^^^^^^^^^^^^^
Nov 29 21:15:24.265 INFO [stderr]    |
Nov 29 21:15:24.265 INFO [stderr]    = note: this `Result` may be an `Err` variant, which should be handled
Nov 29 21:15:24.265 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 21:15:24.265 INFO [stderr] 
Nov 29 21:15:24.265 INFO [stderr] warning: unused `std::result::Result` that must be used
Nov 29 21:15:24.265 INFO [stderr]   --> src/yaml_to_json.rs:95:13
Nov 29 21:15:24.265 INFO [stderr]    |
Nov 29 21:15:24.265 INFO [stderr] 95 |             write!(out, "]");
Nov 29 21:15:24.265 INFO [stderr]    |             ^^^^^^^^^^^^^^^^^
Nov 29 21:15:24.265 INFO [stderr]    |
Nov 29 21:15:24.265 INFO [stderr]    = note: this `Result` may be an `Err` variant, which should be handled
Nov 29 21:15:24.265 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 21:15:24.265 INFO [stderr] 
Nov 29 21:15:24.265 INFO [stderr] warning: unused `std::result::Result` that must be used
Nov 29 21:15:24.265 INFO [stderr]   --> src/yaml_to_json.rs:98:13
Nov 29 21:15:24.265 INFO [stderr]    |
Nov 29 21:15:24.265 INFO [stderr] 98 |             write!(out, "{{");
Nov 29 21:15:24.265 INFO [stderr]    |             ^^^^^^^^^^^^^^^^^^
Nov 29 21:15:24.265 INFO [stderr]    |
Nov 29 21:15:24.265 INFO [stderr]    = note: this `Result` may be an `Err` variant, which should be handled
Nov 29 21:15:24.265 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 21:15:24.265 INFO [stderr] 
Nov 29 21:15:24.265 INFO [stderr] warning: unused `std::result::Result` that must be used
Nov 29 21:15:24.265 INFO [stderr]    --> src/yaml_to_json.rs:105:21
Nov 29 21:15:24.265 INFO [stderr]     |
Nov 29 21:15:24.265 INFO [stderr] 105 |                     write!(out, ",");
Nov 29 21:15:24.265 INFO [stderr]     |                     ^^^^^^^^^^^^^^^^^
Nov 29 21:15:24.265 INFO [stderr]     |
Nov 29 21:15:24.265 INFO [stderr]     = note: this `Result` may be an `Err` variant, which should be handled
Nov 29 21:15:24.265 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 21:15:24.265 INFO [stderr] 
Nov 29 21:15:24.265 INFO [stderr] warning: unused `std::result::Result` that must be used
Nov 29 21:15:24.265 INFO [stderr]    --> src/yaml_to_json.rs:109:21
Nov 29 21:15:24.265 INFO [stderr]     |
Nov 29 21:15:24.265 INFO [stderr] 109 |                     write!(out, ":");
Nov 29 21:15:24.265 INFO [stderr]     |                     ^^^^^^^^^^^^^^^^^
Nov 29 21:15:24.265 INFO [stderr]     |
Nov 29 21:15:24.265 INFO [stderr]     = note: this `Result` may be an `Err` variant, which should be handled
Nov 29 21:15:24.266 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 21:15:24.266 INFO [stderr] 
Nov 29 21:15:24.266 INFO [stderr] warning: unused `std::result::Result` that must be used
Nov 29 21:15:24.266 INFO [stderr]    --> src/yaml_to_json.rs:115:13
Nov 29 21:15:24.266 INFO [stderr]     |
Nov 29 21:15:24.266 INFO [stderr] 115 |             write!(out, "}}");
Nov 29 21:15:24.266 INFO [stderr]     |             ^^^^^^^^^^^^^^^^^^
Nov 29 21:15:24.266 INFO [stderr]     |
Nov 29 21:15:24.266 INFO [stderr]     = note: this `Result` may be an `Err` variant, which should be handled
Nov 29 21:15:24.266 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 21:15:24.266 INFO [stderr] 
Nov 29 21:15:24.266 INFO [stderr] warning: unused `std::result::Result` that must be used
Nov 29 21:15:24.266 INFO [stderr]    --> src/yaml_to_json.rs:118:13
Nov 29 21:15:24.266 INFO [stderr]     |
Nov 29 21:15:24.266 INFO [stderr] 118 |             write!(out, "null");
Nov 29 21:15:24.266 INFO [stderr]     |             ^^^^^^^^^^^^^^^^^^^^
Nov 29 21:15:24.266 INFO [stderr]     |
Nov 29 21:15:24.266 INFO [stderr]     = note: this `Result` may be an `Err` variant, which should be handled
Nov 29 21:15:24.266 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 21:15:24.266 INFO [stderr] 
Nov 29 21:15:24.368 INFO [stderr] warning: unused `std::result::Result` that must be used
Nov 29 21:15:24.368 INFO [stderr]   --> src/yaml_to_json.rs:71:13
Nov 29 21:15:24.368 INFO [stderr]    |
Nov 29 21:15:24.368 INFO [stderr] 71 |             write!(out, "{}", real);
Nov 29 21:15:24.368 INFO [stderr]    |             ^^^^^^^^^^^^^^^^^^^^^^^^
Nov 29 21:15:24.368 INFO [stderr]    |
Nov 29 21:15:24.368 INFO [stderr]    = note: #[warn(unused_must_use)] on by default
Nov 29 21:15:24.368 INFO [stderr]    = note: this `Result` may be an `Err` variant, which should be handled
Nov 29 21:15:24.369 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 21:15:24.369 INFO [stderr] 
Nov 29 21:15:24.369 INFO [stderr] warning: unused `std::result::Result` that must be used
Nov 29 21:15:24.369 INFO [stderr]   --> src/yaml_to_json.rs:74:13
Nov 29 21:15:24.369 INFO [stderr]    |
Nov 29 21:15:24.369 INFO [stderr] 74 |             write!(out, "{}", integer);
Nov 29 21:15:24.369 INFO [stderr]    |             ^^^^^^^^^^^^^^^^^^^^^^^^^^^
Nov 29 21:15:24.369 INFO [stderr]    |
Nov 29 21:15:24.369 INFO [stderr]    = note: this `Result` may be an `Err` variant, which should be handled
Nov 29 21:15:24.369 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 21:15:24.369 INFO [stderr] 
Nov 29 21:15:24.369 INFO [stderr] warning: unused `std::result::Result` that must be used
Nov 29 21:15:24.369 INFO [stderr]   --> src/yaml_to_json.rs:80:13
Nov 29 21:15:24.369 INFO [stderr]    |
Nov 29 21:15:24.369 INFO [stderr] 80 |             write!(out, "{}", boolean);
Nov 29 21:15:24.369 INFO [stderr]    |             ^^^^^^^^^^^^^^^^^^^^^^^^^^^
Nov 29 21:15:24.369 INFO [stderr]    |
Nov 29 21:15:24.369 INFO [stderr]    = note: this `Result` may be an `Err` variant, which should be handled
Nov 29 21:15:24.369 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 21:15:24.369 INFO [stderr] 
Nov 29 21:15:24.369 INFO [stderr] warning: unused `std::result::Result` that must be used
Nov 29 21:15:24.369 INFO [stderr]   --> src/yaml_to_json.rs:83:13
Nov 29 21:15:24.369 INFO [stderr]    |
Nov 29 21:15:24.369 INFO [stderr] 83 |             write!(out, "[");
Nov 29 21:15:24.369 INFO [stderr]    |             ^^^^^^^^^^^^^^^^^
Nov 29 21:15:24.369 INFO [stderr]    |
Nov 29 21:15:24.369 INFO [stderr]    = note: this `Result` may be an `Err` variant, which should be handled
Nov 29 21:15:24.369 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 21:15:24.369 INFO [stderr] 
Nov 29 21:15:24.369 INFO [stderr] warning: unused `std::result::Result` that must be used
Nov 29 21:15:24.369 INFO [stderr]   --> src/yaml_to_json.rs:90:21
Nov 29 21:15:24.369 INFO [stderr]    |
Nov 29 21:15:24.369 INFO [stderr] 90 |                     write!(out, ",");
Nov 29 21:15:24.369 INFO [stderr]    |                     ^^^^^^^^^^^^^^^^^
Nov 29 21:15:24.369 INFO [stderr]    |
Nov 29 21:15:24.369 INFO [stderr]    = note: this `Result` may be an `Err` variant, which should be handled
Nov 29 21:15:24.369 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 21:15:24.369 INFO [stderr] 
Nov 29 21:15:24.369 INFO [stderr] warning: unused `std::result::Result` that must be used
Nov 29 21:15:24.369 INFO [stderr]   --> src/yaml_to_json.rs:95:13
Nov 29 21:15:24.369 INFO [stderr]    |
Nov 29 21:15:24.369 INFO [stderr] 95 |             write!(out, "]");
Nov 29 21:15:24.369 INFO [stderr]    |             ^^^^^^^^^^^^^^^^^
Nov 29 21:15:24.369 INFO [stderr]    |
Nov 29 21:15:24.369 INFO [stderr]    = note: this `Result` may be an `Err` variant, which should be handled
Nov 29 21:15:24.369 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 21:15:24.369 INFO [stderr] 
Nov 29 21:15:24.369 INFO [stderr] warning: unused `std::result::Result` that must be used
Nov 29 21:15:24.369 INFO [stderr]   --> src/yaml_to_json.rs:98:13
Nov 29 21:15:24.369 INFO [stderr]    |
Nov 29 21:15:24.369 INFO [stderr] 98 |             write!(out, "{{");
Nov 29 21:15:24.369 INFO [stderr]    |             ^^^^^^^^^^^^^^^^^^
Nov 29 21:15:24.369 INFO [stderr]    |
Nov 29 21:15:24.369 INFO [stderr]    = note: this `Result` may be an `Err` variant, which should be handled
Nov 29 21:15:24.369 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 21:15:24.369 INFO [stderr] 
Nov 29 21:15:24.369 INFO [stderr] warning: unused `std::result::Result` that must be used
Nov 29 21:15:24.369 INFO [stderr]    --> src/yaml_to_json.rs:105:21
Nov 29 21:15:24.369 INFO [stderr]     |
Nov 29 21:15:24.369 INFO [stderr] 105 |                     write!(out, ",");
Nov 29 21:15:24.369 INFO [stderr]     |                     ^^^^^^^^^^^^^^^^^
Nov 29 21:15:24.369 INFO [stderr]     |
Nov 29 21:15:24.369 INFO [stderr]     = note: this `Result` may be an `Err` variant, which should be handled
Nov 29 21:15:24.369 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 21:15:24.369 INFO [stderr] 
Nov 29 21:15:24.369 INFO [stderr] warning: unused `std::result::Result` that must be used
Nov 29 21:15:24.369 INFO [stderr]    --> src/yaml_to_json.rs:109:21
Nov 29 21:15:24.369 INFO [stderr]     |
Nov 29 21:15:24.369 INFO [stderr] 109 |                     write!(out, ":");
Nov 29 21:15:24.369 INFO [stderr]     |                     ^^^^^^^^^^^^^^^^^
Nov 29 21:15:24.369 INFO [stderr]     |
Nov 29 21:15:24.369 INFO [stderr]     = note: this `Result` may be an `Err` variant, which should be handled
Nov 29 21:15:24.369 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 21:15:24.369 INFO [stderr] 
Nov 29 21:15:24.369 INFO [stderr] warning: unused `std::result::Result` that must be used
Nov 29 21:15:24.369 INFO [stderr]    --> src/yaml_to_json.rs:115:13
Nov 29 21:15:24.369 INFO [stderr]     |
Nov 29 21:15:24.369 INFO [stderr] 115 |             write!(out, "}}");
Nov 29 21:15:24.369 INFO [stderr]     |             ^^^^^^^^^^^^^^^^^^
Nov 29 21:15:24.369 INFO [stderr]     |
Nov 29 21:15:24.369 INFO [stderr]     = note: this `Result` may be an `Err` variant, which should be handled
Nov 29 21:15:24.369 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 21:15:24.369 INFO [stderr] 
Nov 29 21:15:24.369 INFO [stderr] warning: unused `std::result::Result` that must be used
Nov 29 21:15:24.369 INFO [stderr]    --> src/yaml_to_json.rs:118:13
Nov 29 21:15:24.369 INFO [stderr]     |
Nov 29 21:15:24.369 INFO [stderr] 118 |             write!(out, "null");
Nov 29 21:15:24.369 INFO [stderr]     |             ^^^^^^^^^^^^^^^^^^^^
Nov 29 21:15:24.369 INFO [stderr]     |
Nov 29 21:15:24.369 INFO [stderr]     = note: this `Result` may be an `Err` variant, which should be handled
Nov 29 21:15:24.369 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 21:15:24.370 INFO [stderr] 
Nov 29 21:15:24.421 INFO [stderr]     Finished dev [unoptimized + debuginfo] target(s) in 3.12s
Nov 29 21:15:24.436 INFO [stderr] su: No module specific data is present
Nov 29 21:15:25.175 INFO running `"docker" "inspect" "0e54b28254557da6c1d9681fd576b49b2a234f51e035c57ae7454ddbef5d4e7e"`
Nov 29 21:15:25.440 INFO running `"docker" "rm" "-f" "0e54b28254557da6c1d9681fd576b49b2a234f51e035c57ae7454ddbef5d4e7e"`
Nov 29 21:15:25.672 INFO [stdout] 0e54b28254557da6c1d9681fd576b49b2a234f51e035c57ae7454ddbef5d4e7e