Dec 05 12:36:31.078 INFO testing nojima/qurl against try#6eb0fd3ac58f9b16bddb9924a17c3b6c156aa468 for pr-56514
Dec 05 12:36:31.078 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/pr-56514/worker-0/try#6eb0fd3ac58f9b16bddb9924a17c3b6c156aa468:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-0/pr-56514/try#6eb0fd3ac58f9b16bddb9924a17c3b6c156aa468:/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 +6eb0fd3ac58f9b16bddb9924a17c3b6c156aa468-alt build --frozen" "-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 05 12:36:31.264 INFO [stdout] 6b87e220d0d6267693e1d80a60a8c84f267bcb1afa3b415f316c24a79a340802
Dec 05 12:36:31.267 INFO running `"docker" "start" "-a" "6b87e220d0d6267693e1d80a60a8c84f267bcb1afa3b415f316c24a79a340802"`
Dec 05 12:36:31.625 INFO [stderr] usermod: no changes
Dec 05 12:36:32.268 INFO [stderr]    Compiling hyper v0.12.13
Dec 05 12:36:39.546 INFO [stderr]    Compiling qurl v0.1.0 (/source)
Dec 05 12:36:41.231 INFO [stderr] warning: unused `std::result::Result` that must be used
Dec 05 12:36:41.231 INFO [stderr]   --> src/yaml_to_json.rs:71:13
Dec 05 12:36:41.231 INFO [stderr]    |
Dec 05 12:36:41.231 INFO [stderr] 71 |             write!(out, "{}", real);
Dec 05 12:36:41.231 INFO [stderr]    |             ^^^^^^^^^^^^^^^^^^^^^^^^
Dec 05 12:36:41.231 INFO [stderr]    |
Dec 05 12:36:41.231 INFO [stderr]    = note: #[warn(unused_must_use)] on by default
Dec 05 12:36:41.231 INFO [stderr]    = note: this `Result` may be an `Err` variant, which should be handled
Dec 05 12:36:41.231 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 05 12:36:41.231 INFO [stderr] 
Dec 05 12:36:41.231 INFO [stderr] warning: unused `std::result::Result` that must be used
Dec 05 12:36:41.231 INFO [stderr]   --> src/yaml_to_json.rs:74:13
Dec 05 12:36:41.231 INFO [stderr]    |
Dec 05 12:36:41.231 INFO [stderr] 74 |             write!(out, "{}", integer);
Dec 05 12:36:41.231 INFO [stderr]    |             ^^^^^^^^^^^^^^^^^^^^^^^^^^^
Dec 05 12:36:41.231 INFO [stderr]    |
Dec 05 12:36:41.231 INFO [stderr]    = note: this `Result` may be an `Err` variant, which should be handled
Dec 05 12:36:41.231 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 05 12:36:41.231 INFO [stderr] 
Dec 05 12:36:41.231 INFO [stderr] warning: unused `std::result::Result` that must be used
Dec 05 12:36:41.231 INFO [stderr]   --> src/yaml_to_json.rs:80:13
Dec 05 12:36:41.231 INFO [stderr]    |
Dec 05 12:36:41.231 INFO [stderr] 80 |             write!(out, "{}", boolean);
Dec 05 12:36:41.231 INFO [stderr]    |             ^^^^^^^^^^^^^^^^^^^^^^^^^^^
Dec 05 12:36:41.231 INFO [stderr]    |
Dec 05 12:36:41.231 INFO [stderr]    = note: this `Result` may be an `Err` variant, which should be handled
Dec 05 12:36:41.231 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 05 12:36:41.231 INFO [stderr] 
Dec 05 12:36:41.231 INFO [stderr] warning: unused `std::result::Result` that must be used
Dec 05 12:36:41.232 INFO [stderr]   --> src/yaml_to_json.rs:83:13
Dec 05 12:36:41.232 INFO [stderr]    |
Dec 05 12:36:41.232 INFO [stderr] 83 |             write!(out, "[");
Dec 05 12:36:41.232 INFO [stderr]    |             ^^^^^^^^^^^^^^^^^
Dec 05 12:36:41.232 INFO [stderr]    |
Dec 05 12:36:41.232 INFO [stderr]    = note: this `Result` may be an `Err` variant, which should be handled
Dec 05 12:36:41.232 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 05 12:36:41.232 INFO [stderr] 
Dec 05 12:36:41.232 INFO [stderr] warning: unused `std::result::Result` that must be used
Dec 05 12:36:41.232 INFO [stderr]   --> src/yaml_to_json.rs:90:21
Dec 05 12:36:41.232 INFO [stderr]    |
Dec 05 12:36:41.232 INFO [stderr] 90 |                     write!(out, ",");
Dec 05 12:36:41.232 INFO [stderr]    |                     ^^^^^^^^^^^^^^^^^
Dec 05 12:36:41.232 INFO [stderr]    |
Dec 05 12:36:41.232 INFO [stderr]    = note: this `Result` may be an `Err` variant, which should be handled
Dec 05 12:36:41.232 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 05 12:36:41.232 INFO [stderr] 
Dec 05 12:36:41.232 INFO [stderr] warning: unused `std::result::Result` that must be used
Dec 05 12:36:41.232 INFO [stderr]   --> src/yaml_to_json.rs:95:13
Dec 05 12:36:41.232 INFO [stderr]    |
Dec 05 12:36:41.232 INFO [stderr] 95 |             write!(out, "]");
Dec 05 12:36:41.232 INFO [stderr]    |             ^^^^^^^^^^^^^^^^^
Dec 05 12:36:41.232 INFO [stderr]    |
Dec 05 12:36:41.232 INFO [stderr]    = note: this `Result` may be an `Err` variant, which should be handled
Dec 05 12:36:41.232 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 05 12:36:41.232 INFO [stderr] 
Dec 05 12:36:41.232 INFO [stderr] warning: unused `std::result::Result` that must be used
Dec 05 12:36:41.232 INFO [stderr]   --> src/yaml_to_json.rs:98:13
Dec 05 12:36:41.232 INFO [stderr]    |
Dec 05 12:36:41.232 INFO [stderr] 98 |             write!(out, "{{");
Dec 05 12:36:41.232 INFO [stderr]    |             ^^^^^^^^^^^^^^^^^^
Dec 05 12:36:41.232 INFO [stderr]    |
Dec 05 12:36:41.232 INFO [stderr]    = note: this `Result` may be an `Err` variant, which should be handled
Dec 05 12:36:41.232 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 05 12:36:41.232 INFO [stderr] 
Dec 05 12:36:41.232 INFO [stderr] warning: unused `std::result::Result` that must be used
Dec 05 12:36:41.232 INFO [stderr]    --> src/yaml_to_json.rs:105:21
Dec 05 12:36:41.232 INFO [stderr]     |
Dec 05 12:36:41.232 INFO [stderr] 105 |                     write!(out, ",");
Dec 05 12:36:41.232 INFO [stderr]     |                     ^^^^^^^^^^^^^^^^^
Dec 05 12:36:41.232 INFO [stderr]     |
Dec 05 12:36:41.232 INFO [stderr]     = note: this `Result` may be an `Err` variant, which should be handled
Dec 05 12:36:41.232 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 05 12:36:41.232 INFO [stderr] 
Dec 05 12:36:41.232 INFO [stderr] warning: unused `std::result::Result` that must be used
Dec 05 12:36:41.232 INFO [stderr]    --> src/yaml_to_json.rs:109:21
Dec 05 12:36:41.232 INFO [stderr]     |
Dec 05 12:36:41.232 INFO [stderr] 109 |                     write!(out, ":");
Dec 05 12:36:41.232 INFO [stderr]     |                     ^^^^^^^^^^^^^^^^^
Dec 05 12:36:41.232 INFO [stderr]     |
Dec 05 12:36:41.232 INFO [stderr]     = note: this `Result` may be an `Err` variant, which should be handled
Dec 05 12:36:41.232 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 05 12:36:41.233 INFO [stderr] 
Dec 05 12:36:41.233 INFO [stderr] warning: unused `std::result::Result` that must be used
Dec 05 12:36:41.233 INFO [stderr]    --> src/yaml_to_json.rs:115:13
Dec 05 12:36:41.233 INFO [stderr]     |
Dec 05 12:36:41.233 INFO [stderr] 115 |             write!(out, "}}");
Dec 05 12:36:41.233 INFO [stderr]     |             ^^^^^^^^^^^^^^^^^^
Dec 05 12:36:41.233 INFO [stderr]     |
Dec 05 12:36:41.233 INFO [stderr]     = note: this `Result` may be an `Err` variant, which should be handled
Dec 05 12:36:41.233 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 05 12:36:41.233 INFO [stderr] 
Dec 05 12:36:41.233 INFO [stderr] warning: unused `std::result::Result` that must be used
Dec 05 12:36:41.233 INFO [stderr]    --> src/yaml_to_json.rs:118:13
Dec 05 12:36:41.233 INFO [stderr]     |
Dec 05 12:36:41.233 INFO [stderr] 118 |             write!(out, "null");
Dec 05 12:36:41.233 INFO [stderr]     |             ^^^^^^^^^^^^^^^^^^^^
Dec 05 12:36:41.233 INFO [stderr]     |
Dec 05 12:36:41.233 INFO [stderr]     = note: this `Result` may be an `Err` variant, which should be handled
Dec 05 12:36:41.233 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 05 12:36:41.233 INFO [stderr] 
Dec 05 12:36:49.221 INFO [stderr]     Finished dev [unoptimized + debuginfo] target(s) in 17.57s
Dec 05 12:36:49.230 INFO [stderr] su: No module specific data is present
Dec 05 12:36:49.676 INFO running `"docker" "inspect" "6b87e220d0d6267693e1d80a60a8c84f267bcb1afa3b415f316c24a79a340802"`
Dec 05 12:36:49.793 INFO running `"docker" "rm" "-f" "6b87e220d0d6267693e1d80a60a8c84f267bcb1afa3b415f316c24a79a340802"`
Dec 05 12:36:50.004 INFO [stdout] 6b87e220d0d6267693e1d80a60a8c84f267bcb1afa3b415f316c24a79a340802
Dec 05 12:36:50.012 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/pr-56514/worker-0/try#6eb0fd3ac58f9b16bddb9924a17c3b6c156aa468:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-0/pr-56514/try#6eb0fd3ac58f9b16bddb9924a17c3b6c156aa468:/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 +6eb0fd3ac58f9b16bddb9924a17c3b6c156aa468-alt test --frozen --no-run" "-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 05 12:36:50.307 INFO [stdout] 6fde46d8ab0e2cecfed065206ac4d360d3a470f58f0b7f79560b7013daedcbcc
Dec 05 12:36:50.309 INFO running `"docker" "start" "-a" "6fde46d8ab0e2cecfed065206ac4d360d3a470f58f0b7f79560b7013daedcbcc"`
Dec 05 12:36:51.044 INFO [stderr] usermod: no changes
Dec 05 12:36:51.216 INFO [stderr]    Compiling qurl v0.1.0 (/source)
Dec 05 12:36:52.608 INFO [stderr] warning: unused `std::result::Result` that must be used
Dec 05 12:36:52.608 INFO [stderr]   --> src/yaml_to_json.rs:71:13
Dec 05 12:36:52.608 INFO [stderr]    |
Dec 05 12:36:52.608 INFO [stderr] 71 |             write!(out, "{}", real);
Dec 05 12:36:52.608 INFO [stderr]    |             ^^^^^^^^^^^^^^^^^^^^^^^^
Dec 05 12:36:52.612 INFO [stderr]    |
Dec 05 12:36:52.612 INFO [stderr]    = note: #[warn(unused_must_use)] on by default
Dec 05 12:36:52.612 INFO [stderr]    = note: this `Result` may be an `Err` variant, which should be handled
Dec 05 12:36:52.612 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 05 12:36:52.612 INFO [stderr] 
Dec 05 12:36:52.612 INFO [stderr] warning: unused `std::result::Result` that must be used
Dec 05 12:36:52.612 INFO [stderr]   --> src/yaml_to_json.rs:74:13
Dec 05 12:36:52.612 INFO [stderr]    |
Dec 05 12:36:52.612 INFO [stderr] 74 |             write!(out, "{}", integer);
Dec 05 12:36:52.612 INFO [stderr]    |             ^^^^^^^^^^^^^^^^^^^^^^^^^^^
Dec 05 12:36:52.612 INFO [stderr]    |
Dec 05 12:36:52.612 INFO [stderr]    = note: this `Result` may be an `Err` variant, which should be handled
Dec 05 12:36:52.612 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 05 12:36:52.612 INFO [stderr] 
Dec 05 12:36:52.612 INFO [stderr] warning: unused `std::result::Result` that must be used
Dec 05 12:36:52.612 INFO [stderr]   --> src/yaml_to_json.rs:80:13
Dec 05 12:36:52.612 INFO [stderr]    |
Dec 05 12:36:52.612 INFO [stderr] 80 |             write!(out, "{}", boolean);
Dec 05 12:36:52.612 INFO [stderr]    |             ^^^^^^^^^^^^^^^^^^^^^^^^^^^
Dec 05 12:36:52.612 INFO [stderr]    |
Dec 05 12:36:52.612 INFO [stderr]    = note: this `Result` may be an `Err` variant, which should be handled
Dec 05 12:36:52.612 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 05 12:36:52.612 INFO [stderr] 
Dec 05 12:36:52.612 INFO [stderr] warning: unused `std::result::Result` that must be used
Dec 05 12:36:52.612 INFO [stderr]   --> src/yaml_to_json.rs:83:13
Dec 05 12:36:52.612 INFO [stderr]    |
Dec 05 12:36:52.612 INFO [stderr] 83 |             write!(out, "[");
Dec 05 12:36:52.612 INFO [stderr]    |             ^^^^^^^^^^^^^^^^^
Dec 05 12:36:52.612 INFO [stderr]    |
Dec 05 12:36:52.612 INFO [stderr]    = note: this `Result` may be an `Err` variant, which should be handled
Dec 05 12:36:52.612 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 05 12:36:52.612 INFO [stderr] 
Dec 05 12:36:52.612 INFO [stderr] warning: unused `std::result::Result` that must be used
Dec 05 12:36:52.612 INFO [stderr]   --> src/yaml_to_json.rs:90:21
Dec 05 12:36:52.612 INFO [stderr]    |
Dec 05 12:36:52.612 INFO [stderr] 90 |                     write!(out, ",");
Dec 05 12:36:52.612 INFO [stderr]    |                     ^^^^^^^^^^^^^^^^^
Dec 05 12:36:52.612 INFO [stderr]    |
Dec 05 12:36:52.612 INFO [stderr]    = note: this `Result` may be an `Err` variant, which should be handled
Dec 05 12:36:52.612 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 05 12:36:52.612 INFO [stderr] 
Dec 05 12:36:52.613 INFO [stderr] warning: unused `std::result::Result` that must be used
Dec 05 12:36:52.613 INFO [stderr]   --> src/yaml_to_json.rs:95:13
Dec 05 12:36:52.613 INFO [stderr]    |
Dec 05 12:36:52.613 INFO [stderr] 95 |             write!(out, "]");
Dec 05 12:36:52.613 INFO [stderr]    |             ^^^^^^^^^^^^^^^^^
Dec 05 12:36:52.613 INFO [stderr]    |
Dec 05 12:36:52.613 INFO [stderr]    = note: this `Result` may be an `Err` variant, which should be handled
Dec 05 12:36:52.613 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 05 12:36:52.613 INFO [stderr] 
Dec 05 12:36:52.613 INFO [stderr] warning: unused `std::result::Result` that must be used
Dec 05 12:36:52.613 INFO [stderr]   --> src/yaml_to_json.rs:98:13
Dec 05 12:36:52.613 INFO [stderr]    |
Dec 05 12:36:52.613 INFO [stderr] 98 |             write!(out, "{{");
Dec 05 12:36:52.613 INFO [stderr]    |             ^^^^^^^^^^^^^^^^^^
Dec 05 12:36:52.613 INFO [stderr]    |
Dec 05 12:36:52.613 INFO [stderr]    = note: this `Result` may be an `Err` variant, which should be handled
Dec 05 12:36:52.613 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 05 12:36:52.613 INFO [stderr] 
Dec 05 12:36:52.613 INFO [stderr] warning: unused `std::result::Result` that must be used
Dec 05 12:36:52.613 INFO [stderr]    --> src/yaml_to_json.rs:105:21
Dec 05 12:36:52.613 INFO [stderr]     |
Dec 05 12:36:52.613 INFO [stderr] 105 |                     write!(out, ",");
Dec 05 12:36:52.613 INFO [stderr]     |                     ^^^^^^^^^^^^^^^^^
Dec 05 12:36:52.613 INFO [stderr]     |
Dec 05 12:36:52.613 INFO [stderr]     = note: this `Result` may be an `Err` variant, which should be handled
Dec 05 12:36:52.613 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 05 12:36:52.613 INFO [stderr] 
Dec 05 12:36:52.613 INFO [stderr] warning: unused `std::result::Result` that must be used
Dec 05 12:36:52.613 INFO [stderr]    --> src/yaml_to_json.rs:109:21
Dec 05 12:36:52.613 INFO [stderr]     |
Dec 05 12:36:52.613 INFO [stderr] 109 |                     write!(out, ":");
Dec 05 12:36:52.613 INFO [stderr]     |                     ^^^^^^^^^^^^^^^^^
Dec 05 12:36:52.613 INFO [stderr]     |
Dec 05 12:36:52.613 INFO [stderr]     = note: this `Result` may be an `Err` variant, which should be handled
Dec 05 12:36:52.613 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 05 12:36:52.613 INFO [stderr] 
Dec 05 12:36:52.616 INFO [stderr] warning: unused `std::result::Result` that must be used
Dec 05 12:36:52.616 INFO [stderr]    --> src/yaml_to_json.rs:115:13
Dec 05 12:36:52.616 INFO [stderr]     |
Dec 05 12:36:52.616 INFO [stderr] 115 |             write!(out, "}}");
Dec 05 12:36:52.616 INFO [stderr]     |             ^^^^^^^^^^^^^^^^^^
Dec 05 12:36:52.616 INFO [stderr]     |
Dec 05 12:36:52.616 INFO [stderr]     = note: this `Result` may be an `Err` variant, which should be handled
Dec 05 12:36:52.616 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 05 12:36:52.616 INFO [stderr] 
Dec 05 12:36:52.616 INFO [stderr] warning: unused `std::result::Result` that must be used
Dec 05 12:36:52.616 INFO [stderr]    --> src/yaml_to_json.rs:118:13
Dec 05 12:36:52.616 INFO [stderr]     |
Dec 05 12:36:52.616 INFO [stderr] 118 |             write!(out, "null");
Dec 05 12:36:52.616 INFO [stderr]     |             ^^^^^^^^^^^^^^^^^^^^
Dec 05 12:36:52.616 INFO [stderr]     |
Dec 05 12:36:52.616 INFO [stderr]     = note: this `Result` may be an `Err` variant, which should be handled
Dec 05 12:36:52.616 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 05 12:36:52.616 INFO [stderr] 
Dec 05 12:36:54.300 INFO [stderr]     Finished dev [unoptimized + debuginfo] target(s) in 3.23s
Dec 05 12:36:54.311 INFO [stderr] su: No module specific data is present
Dec 05 12:36:55.036 INFO running `"docker" "inspect" "6fde46d8ab0e2cecfed065206ac4d360d3a470f58f0b7f79560b7013daedcbcc"`
Dec 05 12:36:55.314 INFO running `"docker" "rm" "-f" "6fde46d8ab0e2cecfed065206ac4d360d3a470f58f0b7f79560b7013daedcbcc"`
Dec 05 12:36:55.593 INFO [stdout] 6fde46d8ab0e2cecfed065206ac4d360d3a470f58f0b7f79560b7013daedcbcc
Dec 05 12:36:55.597 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/pr-56514/worker-0/try#6eb0fd3ac58f9b16bddb9924a17c3b6c156aa468:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-0/pr-56514/try#6eb0fd3ac58f9b16bddb9924a17c3b6c156aa468:/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 +6eb0fd3ac58f9b16bddb9924a17c3b6c156aa468-alt test --frozen" "-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 05 12:36:55.928 INFO [stdout] aac484aa417bd25fa0c542626c630d084e498e5fde854605cf4eaa45fd625b71
Dec 05 12:36:55.936 INFO running `"docker" "start" "-a" "aac484aa417bd25fa0c542626c630d084e498e5fde854605cf4eaa45fd625b71"`
Dec 05 12:36:56.530 INFO [stderr] usermod: no changes
Dec 05 12:36:56.634 INFO [stderr]     Finished dev [unoptimized + debuginfo] target(s) in 0.08s
Dec 05 12:36:56.648 INFO [stderr]      Running /target/debug/deps/qurl-a58b3a748bb8d983
Dec 05 12:36:56.650 INFO [stdout] 
Dec 05 12:36:56.650 INFO [stdout] running 7 tests
Dec 05 12:36:56.651 INFO [stdout] test yaml_to_json::test_boolean ... ok
Dec 05 12:36:56.651 INFO [stdout] test yaml_to_json::test_hash ... ok
Dec 05 12:36:56.651 INFO [stdout] test yaml_to_json::test_integer ... ok
Dec 05 12:36:56.651 INFO [stdout] test yaml_to_json::test_real ... ok
Dec 05 12:36:56.651 INFO [stdout] test yaml_to_json::test_null ... ok
Dec 05 12:36:56.651 INFO [stdout] test yaml_to_json::test_string ... ok
Dec 05 12:36:56.652 INFO [stdout] test yaml_to_json::test_array ... ok
Dec 05 12:36:56.652 INFO [stdout] 
Dec 05 12:36:56.652 INFO [stdout] test result: ok. 7 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out
Dec 05 12:36:56.652 INFO [stdout] 
Dec 05 12:36:56.655 INFO [stderr] su: No module specific data is present
Dec 05 12:36:56.920 INFO running `"docker" "inspect" "aac484aa417bd25fa0c542626c630d084e498e5fde854605cf4eaa45fd625b71"`
Dec 05 12:36:57.028 INFO running `"docker" "rm" "-f" "aac484aa417bd25fa0c542626c630d084e498e5fde854605cf4eaa45fd625b71"`
Dec 05 12:36:57.166 INFO [stdout] aac484aa417bd25fa0c542626c630d084e498e5fde854605cf4eaa45fd625b71