Dec 05 12:36:31.310 INFO testing nojima/qurl against master#906deae0790bd18681b937fe9a141a3c26cf1855 for pr-56514
Dec 05 12:36:31.310 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/pr-56514/worker-4/master#906deae0790bd18681b937fe9a141a3c26cf1855:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-4/pr-56514/master#906deae0790bd18681b937fe9a141a3c26cf1855:/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 +906deae0790bd18681b937fe9a141a3c26cf1855-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.507 INFO [stdout] 766be5e1d037c7932269f83de2e5a3b2398743ab67ed0741008eb47f619dbc9b
Dec 05 12:36:31.514 INFO running `"docker" "start" "-a" "766be5e1d037c7932269f83de2e5a3b2398743ab67ed0741008eb47f619dbc9b"`
Dec 05 12:36:31.960 INFO [stderr] usermod: no changes
Dec 05 12:36:32.362 INFO [stderr]    Compiling hyper v0.12.13
Dec 05 12:36:40.056 INFO [stderr]    Compiling qurl v0.1.0 (/source)
Dec 05 12:36:41.710 INFO [stderr] warning: unused `std::result::Result` that must be used
Dec 05 12:36:41.710 INFO [stderr]   --> src/yaml_to_json.rs:71:13
Dec 05 12:36:41.710 INFO [stderr]    |
Dec 05 12:36:41.710 INFO [stderr] 71 |             write!(out, "{}", real);
Dec 05 12:36:41.710 INFO [stderr]    |             ^^^^^^^^^^^^^^^^^^^^^^^^
Dec 05 12:36:41.710 INFO [stderr]    |
Dec 05 12:36:41.710 INFO [stderr]    = note: #[warn(unused_must_use)] on by default
Dec 05 12:36:41.710 INFO [stderr]    = note: this `Result` may be an `Err` variant, which should be handled
Dec 05 12:36:41.710 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.710 INFO [stderr] 
Dec 05 12:36:41.710 INFO [stderr] warning: unused `std::result::Result` that must be used
Dec 05 12:36:41.710 INFO [stderr]   --> src/yaml_to_json.rs:74:13
Dec 05 12:36:41.710 INFO [stderr]    |
Dec 05 12:36:41.710 INFO [stderr] 74 |             write!(out, "{}", integer);
Dec 05 12:36:41.710 INFO [stderr]    |             ^^^^^^^^^^^^^^^^^^^^^^^^^^^
Dec 05 12:36:41.710 INFO [stderr]    |
Dec 05 12:36:41.710 INFO [stderr]    = note: this `Result` may be an `Err` variant, which should be handled
Dec 05 12:36:41.710 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.710 INFO [stderr] 
Dec 05 12:36:41.710 INFO [stderr] warning: unused `std::result::Result` that must be used
Dec 05 12:36:41.710 INFO [stderr]   --> src/yaml_to_json.rs:80:13
Dec 05 12:36:41.710 INFO [stderr]    |
Dec 05 12:36:41.710 INFO [stderr] 80 |             write!(out, "{}", boolean);
Dec 05 12:36:41.710 INFO [stderr]    |             ^^^^^^^^^^^^^^^^^^^^^^^^^^^
Dec 05 12:36:41.710 INFO [stderr]    |
Dec 05 12:36:41.710 INFO [stderr]    = note: this `Result` may be an `Err` variant, which should be handled
Dec 05 12:36:41.710 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.711 INFO [stderr] 
Dec 05 12:36:41.711 INFO [stderr] warning: unused `std::result::Result` that must be used
Dec 05 12:36:41.711 INFO [stderr]   --> src/yaml_to_json.rs:83:13
Dec 05 12:36:41.711 INFO [stderr]    |
Dec 05 12:36:41.711 INFO [stderr] 83 |             write!(out, "[");
Dec 05 12:36:41.711 INFO [stderr]    |             ^^^^^^^^^^^^^^^^^
Dec 05 12:36:41.711 INFO [stderr]    |
Dec 05 12:36:41.711 INFO [stderr]    = note: this `Result` may be an `Err` variant, which should be handled
Dec 05 12:36:41.716 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.716 INFO [stderr] 
Dec 05 12:36:41.716 INFO [stderr] warning: unused `std::result::Result` that must be used
Dec 05 12:36:41.716 INFO [stderr]   --> src/yaml_to_json.rs:90:21
Dec 05 12:36:41.716 INFO [stderr]    |
Dec 05 12:36:41.716 INFO [stderr] 90 |                     write!(out, ",");
Dec 05 12:36:41.716 INFO [stderr]    |                     ^^^^^^^^^^^^^^^^^
Dec 05 12:36:41.716 INFO [stderr]    |
Dec 05 12:36:41.716 INFO [stderr]    = note: this `Result` may be an `Err` variant, which should be handled
Dec 05 12:36:41.716 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.716 INFO [stderr] 
Dec 05 12:36:41.716 INFO [stderr] warning: unused `std::result::Result` that must be used
Dec 05 12:36:41.716 INFO [stderr]   --> src/yaml_to_json.rs:95:13
Dec 05 12:36:41.716 INFO [stderr]    |
Dec 05 12:36:41.716 INFO [stderr] 95 |             write!(out, "]");
Dec 05 12:36:41.716 INFO [stderr]    |             ^^^^^^^^^^^^^^^^^
Dec 05 12:36:41.716 INFO [stderr]    |
Dec 05 12:36:41.716 INFO [stderr]    = note: this `Result` may be an `Err` variant, which should be handled
Dec 05 12:36:41.716 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.716 INFO [stderr] 
Dec 05 12:36:41.716 INFO [stderr] warning: unused `std::result::Result` that must be used
Dec 05 12:36:41.716 INFO [stderr]   --> src/yaml_to_json.rs:98:13
Dec 05 12:36:41.716 INFO [stderr]    |
Dec 05 12:36:41.716 INFO [stderr] 98 |             write!(out, "{{");
Dec 05 12:36:41.716 INFO [stderr]    |             ^^^^^^^^^^^^^^^^^^
Dec 05 12:36:41.716 INFO [stderr]    |
Dec 05 12:36:41.716 INFO [stderr]    = note: this `Result` may be an `Err` variant, which should be handled
Dec 05 12:36:41.716 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.716 INFO [stderr] 
Dec 05 12:36:41.716 INFO [stderr] warning: unused `std::result::Result` that must be used
Dec 05 12:36:41.716 INFO [stderr]    --> src/yaml_to_json.rs:105:21
Dec 05 12:36:41.716 INFO [stderr]     |
Dec 05 12:36:41.717 INFO [stderr] 105 |                     write!(out, ",");
Dec 05 12:36:41.717 INFO [stderr]     |                     ^^^^^^^^^^^^^^^^^
Dec 05 12:36:41.717 INFO [stderr]     |
Dec 05 12:36:41.717 INFO [stderr]     = note: this `Result` may be an `Err` variant, which should be handled
Dec 05 12:36:41.717 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.717 INFO [stderr] 
Dec 05 12:36:41.717 INFO [stderr] warning: unused `std::result::Result` that must be used
Dec 05 12:36:41.717 INFO [stderr]    --> src/yaml_to_json.rs:109:21
Dec 05 12:36:41.717 INFO [stderr]     |
Dec 05 12:36:41.717 INFO [stderr] 109 |                     write!(out, ":");
Dec 05 12:36:41.717 INFO [stderr]     |                     ^^^^^^^^^^^^^^^^^
Dec 05 12:36:41.717 INFO [stderr]     |
Dec 05 12:36:41.717 INFO [stderr]     = note: this `Result` may be an `Err` variant, which should be handled
Dec 05 12:36:41.717 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.717 INFO [stderr] 
Dec 05 12:36:41.717 INFO [stderr] warning: unused `std::result::Result` that must be used
Dec 05 12:36:41.717 INFO [stderr]    --> src/yaml_to_json.rs:115:13
Dec 05 12:36:41.717 INFO [stderr]     |
Dec 05 12:36:41.717 INFO [stderr] 115 |             write!(out, "}}");
Dec 05 12:36:41.717 INFO [stderr]     |             ^^^^^^^^^^^^^^^^^^
Dec 05 12:36:41.717 INFO [stderr]     |
Dec 05 12:36:41.717 INFO [stderr]     = note: this `Result` may be an `Err` variant, which should be handled
Dec 05 12:36:41.717 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.717 INFO [stderr] 
Dec 05 12:36:41.717 INFO [stderr] warning: unused `std::result::Result` that must be used
Dec 05 12:36:41.717 INFO [stderr]    --> src/yaml_to_json.rs:118:13
Dec 05 12:36:41.717 INFO [stderr]     |
Dec 05 12:36:41.717 INFO [stderr] 118 |             write!(out, "null");
Dec 05 12:36:41.717 INFO [stderr]     |             ^^^^^^^^^^^^^^^^^^^^
Dec 05 12:36:41.717 INFO [stderr]     |
Dec 05 12:36:41.717 INFO [stderr]     = note: this `Result` may be an `Err` variant, which should be handled
Dec 05 12:36:41.717 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.717 INFO [stderr] 
Dec 05 12:36:49.595 INFO [stderr]     Finished dev [unoptimized + debuginfo] target(s) in 17.62s
Dec 05 12:36:49.602 INFO [stderr] su: No module specific data is present
Dec 05 12:36:49.906 INFO running `"docker" "inspect" "766be5e1d037c7932269f83de2e5a3b2398743ab67ed0741008eb47f619dbc9b"`
Dec 05 12:36:50.083 INFO running `"docker" "rm" "-f" "766be5e1d037c7932269f83de2e5a3b2398743ab67ed0741008eb47f619dbc9b"`
Dec 05 12:36:50.265 INFO [stdout] 766be5e1d037c7932269f83de2e5a3b2398743ab67ed0741008eb47f619dbc9b
Dec 05 12:36:50.270 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/pr-56514/worker-4/master#906deae0790bd18681b937fe9a141a3c26cf1855:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-4/pr-56514/master#906deae0790bd18681b937fe9a141a3c26cf1855:/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 +906deae0790bd18681b937fe9a141a3c26cf1855-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.553 INFO [stdout] 4e545ee8366b190ef3f1d57cd6f95d97bd819ccef15d7fd2dc0d8d40344da2cc
Dec 05 12:36:50.558 INFO running `"docker" "start" "-a" "4e545ee8366b190ef3f1d57cd6f95d97bd819ccef15d7fd2dc0d8d40344da2cc"`
Dec 05 12:36:51.136 INFO [stderr] usermod: no changes
Dec 05 12:36:51.276 INFO [stderr]    Compiling qurl v0.1.0 (/source)
Dec 05 12:36:52.802 INFO [stderr] warning: unused `std::result::Result` that must be used
Dec 05 12:36:52.802 INFO [stderr]   --> src/yaml_to_json.rs:71:13
Dec 05 12:36:52.802 INFO [stderr]    |
Dec 05 12:36:52.802 INFO [stderr] 71 |             write!(out, "{}", real);
Dec 05 12:36:52.802 INFO [stderr]    |             ^^^^^^^^^^^^^^^^^^^^^^^^
Dec 05 12:36:52.802 INFO [stderr]    |
Dec 05 12:36:52.802 INFO [stderr]    = note: #[warn(unused_must_use)] on by default
Dec 05 12:36:52.802 INFO [stderr]    = note: this `Result` may be an `Err` variant, which should be handled
Dec 05 12:36:52.802 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.802 INFO [stderr] 
Dec 05 12:36:52.802 INFO [stderr] warning: unused `std::result::Result` that must be used
Dec 05 12:36:52.802 INFO [stderr]   --> src/yaml_to_json.rs:74:13
Dec 05 12:36:52.802 INFO [stderr]    |
Dec 05 12:36:52.802 INFO [stderr] 74 |             write!(out, "{}", integer);
Dec 05 12:36:52.802 INFO [stderr]    |             ^^^^^^^^^^^^^^^^^^^^^^^^^^^
Dec 05 12:36:52.802 INFO [stderr]    |
Dec 05 12:36:52.802 INFO [stderr]    = note: this `Result` may be an `Err` variant, which should be handled
Dec 05 12:36:52.802 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.802 INFO [stderr] 
Dec 05 12:36:52.802 INFO [stderr] warning: unused `std::result::Result` that must be used
Dec 05 12:36:52.802 INFO [stderr]   --> src/yaml_to_json.rs:80:13
Dec 05 12:36:52.802 INFO [stderr]    |
Dec 05 12:36:52.803 INFO [stderr] 80 |             write!(out, "{}", boolean);
Dec 05 12:36:52.803 INFO [stderr]    |             ^^^^^^^^^^^^^^^^^^^^^^^^^^^
Dec 05 12:36:52.803 INFO [stderr]    |
Dec 05 12:36:52.803 INFO [stderr]    = note: this `Result` may be an `Err` variant, which should be handled
Dec 05 12:36:52.803 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.803 INFO [stderr] 
Dec 05 12:36:52.803 INFO [stderr] warning: unused `std::result::Result` that must be used
Dec 05 12:36:52.803 INFO [stderr]   --> src/yaml_to_json.rs:83:13
Dec 05 12:36:52.803 INFO [stderr]    |
Dec 05 12:36:52.803 INFO [stderr] 83 |             write!(out, "[");
Dec 05 12:36:52.803 INFO [stderr]    |             ^^^^^^^^^^^^^^^^^
Dec 05 12:36:52.803 INFO [stderr]    |
Dec 05 12:36:52.803 INFO [stderr]    = note: this `Result` may be an `Err` variant, which should be handled
Dec 05 12:36:52.803 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.803 INFO [stderr] 
Dec 05 12:36:52.803 INFO [stderr] warning: unused `std::result::Result` that must be used
Dec 05 12:36:52.803 INFO [stderr]   --> src/yaml_to_json.rs:90:21
Dec 05 12:36:52.803 INFO [stderr]    |
Dec 05 12:36:52.803 INFO [stderr] 90 |                     write!(out, ",");
Dec 05 12:36:52.803 INFO [stderr]    |                     ^^^^^^^^^^^^^^^^^
Dec 05 12:36:52.803 INFO [stderr]    |
Dec 05 12:36:52.803 INFO [stderr]    = note: this `Result` may be an `Err` variant, which should be handled
Dec 05 12:36:52.803 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.803 INFO [stderr] 
Dec 05 12:36:52.803 INFO [stderr] warning: unused `std::result::Result` that must be used
Dec 05 12:36:52.803 INFO [stderr]   --> src/yaml_to_json.rs:95:13
Dec 05 12:36:52.803 INFO [stderr]    |
Dec 05 12:36:52.803 INFO [stderr] 95 |             write!(out, "]");
Dec 05 12:36:52.803 INFO [stderr]    |             ^^^^^^^^^^^^^^^^^
Dec 05 12:36:52.803 INFO [stderr]    |
Dec 05 12:36:52.803 INFO [stderr]    = note: this `Result` may be an `Err` variant, which should be handled
Dec 05 12:36:52.803 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.803 INFO [stderr] 
Dec 05 12:36:52.803 INFO [stderr] warning: unused `std::result::Result` that must be used
Dec 05 12:36:52.803 INFO [stderr]   --> src/yaml_to_json.rs:98:13
Dec 05 12:36:52.803 INFO [stderr]    |
Dec 05 12:36:52.803 INFO [stderr] 98 |             write!(out, "{{");
Dec 05 12:36:52.803 INFO [stderr]    |             ^^^^^^^^^^^^^^^^^^
Dec 05 12:36:52.803 INFO [stderr]    |
Dec 05 12:36:52.803 INFO [stderr]    = note: this `Result` may be an `Err` variant, which should be handled
Dec 05 12:36:52.803 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.803 INFO [stderr] 
Dec 05 12:36:52.803 INFO [stderr] warning: unused `std::result::Result` that must be used
Dec 05 12:36:52.808 INFO [stderr]    --> src/yaml_to_json.rs:105:21
Dec 05 12:36:52.808 INFO [stderr]     |
Dec 05 12:36:52.808 INFO [stderr] 105 |                     write!(out, ",");
Dec 05 12:36:52.808 INFO [stderr]     |                     ^^^^^^^^^^^^^^^^^
Dec 05 12:36:52.808 INFO [stderr]     |
Dec 05 12:36:52.808 INFO [stderr]     = note: this `Result` may be an `Err` variant, which should be handled
Dec 05 12:36:52.808 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.808 INFO [stderr] 
Dec 05 12:36:52.808 INFO [stderr] warning: unused `std::result::Result` that must be used
Dec 05 12:36:52.808 INFO [stderr]    --> src/yaml_to_json.rs:109:21
Dec 05 12:36:52.808 INFO [stderr]     |
Dec 05 12:36:52.808 INFO [stderr] 109 |                     write!(out, ":");
Dec 05 12:36:52.808 INFO [stderr]     |                     ^^^^^^^^^^^^^^^^^
Dec 05 12:36:52.808 INFO [stderr]     |
Dec 05 12:36:52.808 INFO [stderr]     = note: this `Result` may be an `Err` variant, which should be handled
Dec 05 12:36:52.808 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.808 INFO [stderr] 
Dec 05 12:36:52.809 INFO [stderr] warning: unused `std::result::Result` that must be used
Dec 05 12:36:52.809 INFO [stderr]    --> src/yaml_to_json.rs:115:13
Dec 05 12:36:52.809 INFO [stderr]     |
Dec 05 12:36:52.810 INFO [stderr] 115 |             write!(out, "}}");
Dec 05 12:36:52.810 INFO [stderr]     |             ^^^^^^^^^^^^^^^^^^
Dec 05 12:36:52.810 INFO [stderr]     |
Dec 05 12:36:52.810 INFO [stderr]     = note: this `Result` may be an `Err` variant, which should be handled
Dec 05 12:36:52.810 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.810 INFO [stderr] 
Dec 05 12:36:52.810 INFO [stderr] warning: unused `std::result::Result` that must be used
Dec 05 12:36:52.810 INFO [stderr]    --> src/yaml_to_json.rs:118:13
Dec 05 12:36:52.810 INFO [stderr]     |
Dec 05 12:36:52.816 INFO [stderr] 118 |             write!(out, "null");
Dec 05 12:36:52.816 INFO [stderr]     |             ^^^^^^^^^^^^^^^^^^^^
Dec 05 12:36:52.816 INFO [stderr]     |
Dec 05 12:36:52.816 INFO [stderr]     = note: this `Result` may be an `Err` variant, which should be handled
Dec 05 12:36:52.816 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.816 INFO [stderr] 
Dec 05 12:36:54.468 INFO [stderr]     Finished dev [unoptimized + debuginfo] target(s) in 3.30s
Dec 05 12:36:54.481 INFO [stderr] su: No module specific data is present
Dec 05 12:36:55.166 INFO running `"docker" "inspect" "4e545ee8366b190ef3f1d57cd6f95d97bd819ccef15d7fd2dc0d8d40344da2cc"`
Dec 05 12:36:55.462 INFO running `"docker" "rm" "-f" "4e545ee8366b190ef3f1d57cd6f95d97bd819ccef15d7fd2dc0d8d40344da2cc"`
Dec 05 12:36:55.660 INFO [stdout] 4e545ee8366b190ef3f1d57cd6f95d97bd819ccef15d7fd2dc0d8d40344da2cc
Dec 05 12:36:55.666 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/pr-56514/worker-4/master#906deae0790bd18681b937fe9a141a3c26cf1855:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-4/pr-56514/master#906deae0790bd18681b937fe9a141a3c26cf1855:/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 +906deae0790bd18681b937fe9a141a3c26cf1855-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:56.068 INFO [stdout] ccea142801cc50d1b98d3d7986863681defd30782de1dbd209fbef80ea9754e1
Dec 05 12:36:56.074 INFO running `"docker" "start" "-a" "ccea142801cc50d1b98d3d7986863681defd30782de1dbd209fbef80ea9754e1"`
Dec 05 12:36:56.615 INFO [stderr] usermod: no changes
Dec 05 12:36:56.744 INFO [stderr]     Finished dev [unoptimized + debuginfo] target(s) in 0.11s
Dec 05 12:36:56.749 INFO [stderr]      Running /target/debug/deps/qurl-efb6974c03f17740
Dec 05 12:36:56.751 INFO [stdout] 
Dec 05 12:36:56.751 INFO [stdout] running 7 tests
Dec 05 12:36:56.752 INFO [stdout] test yaml_to_json::test_null ... ok
Dec 05 12:36:56.752 INFO [stdout] test yaml_to_json::test_boolean ... ok
Dec 05 12:36:56.752 INFO [stdout] test yaml_to_json::test_string ... ok
Dec 05 12:36:56.752 INFO [stdout] test yaml_to_json::test_hash ... ok
Dec 05 12:36:56.752 INFO [stdout] test yaml_to_json::test_real ... ok
Dec 05 12:36:56.752 INFO [stdout] test yaml_to_json::test_integer ... ok
Dec 05 12:36:56.754 INFO [stdout] test yaml_to_json::test_array ... ok
Dec 05 12:36:56.754 INFO [stdout] 
Dec 05 12:36:56.754 INFO [stdout] test result: ok. 7 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out
Dec 05 12:36:56.754 INFO [stdout] 
Dec 05 12:36:56.755 INFO [stderr] su: No module specific data is present
Dec 05 12:36:57.028 INFO running `"docker" "inspect" "ccea142801cc50d1b98d3d7986863681defd30782de1dbd209fbef80ea9754e1"`
Dec 05 12:36:57.171 INFO running `"docker" "rm" "-f" "ccea142801cc50d1b98d3d7986863681defd30782de1dbd209fbef80ea9754e1"`
Dec 05 12:36:57.312 INFO [stdout] ccea142801cc50d1b98d3d7986863681defd30782de1dbd209fbef80ea9754e1