Dec 05 19:10:51.681 INFO testing juli1/rust-json-example against master#906deae0790bd18681b937fe9a141a3c26cf1855 for pr-56514
Dec 05 19:10:51.681 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/pr-56514/worker-5/master#906deae0790bd18681b937fe9a141a3c26cf1855:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-5/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 19:10:52.017 INFO [stdout] e2f8ca46b601b197aa5cd735d9b5edf08dd10140ace5372eec5c1d4094eb9764
Dec 05 19:10:52.019 INFO running `"docker" "start" "-a" "e2f8ca46b601b197aa5cd735d9b5edf08dd10140ace5372eec5c1d4094eb9764"`
Dec 05 19:10:52.630 INFO [stderr] usermod: no changes
Dec 05 19:10:52.660 INFO [stderr] warning: An explicit [[bin]] section is specified in Cargo.toml which currently
Dec 05 19:10:52.660 INFO [stderr] disables Cargo from automatically inferring other binary targets.
Dec 05 19:10:52.660 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following
Dec 05 19:10:52.660 INFO [stderr] files will be included as a binary target:
Dec 05 19:10:52.660 INFO [stderr] 
Dec 05 19:10:52.660 INFO [stderr] * /source/src/main.rs
Dec 05 19:10:52.660 INFO [stderr] 
Dec 05 19:10:52.660 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be
Dec 05 19:10:52.660 INFO [stderr] ready to be compiled as a binary target today. You can future-proof yourself
Dec 05 19:10:52.660 INFO [stderr] and disable this warning by adding `autobins = false` to your [package]
Dec 05 19:10:52.660 INFO [stderr] section. You may also move the files to a location where Cargo would not
Dec 05 19:10:52.660 INFO [stderr] automatically infer them to be a target, such as in subfolders.
Dec 05 19:10:52.660 INFO [stderr] 
Dec 05 19:10:52.660 INFO [stderr] For more information on this warning you can consult
Dec 05 19:10:52.660 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330
Dec 05 19:10:52.835 INFO [stderr]    Compiling tokio v0.0.0
Dec 05 19:10:52.837 INFO [stderr]    Compiling futures-cpupool v0.1.8
Dec 05 19:10:52.844 INFO [stderr]    Compiling http v0.1.4
Dec 05 19:10:52.845 INFO [stderr]    Compiling tokio-tls v0.1.4
Dec 05 19:10:53.823 INFO [stderr]    Compiling hyper v0.11.16
Dec 05 19:11:01.688 INFO [stderr]    Compiling hyper-tls v0.1.2
Dec 05 19:11:03.038 INFO [stderr]    Compiling rust-json v0.1.0 (/source)
Dec 05 19:11:07.785 INFO [stderr]     Finished dev [unoptimized + debuginfo] target(s) in 15.13s
Dec 05 19:11:07.797 INFO [stderr] su: No module specific data is present
Dec 05 19:11:08.070 INFO running `"docker" "inspect" "e2f8ca46b601b197aa5cd735d9b5edf08dd10140ace5372eec5c1d4094eb9764"`
Dec 05 19:11:08.218 INFO running `"docker" "rm" "-f" "e2f8ca46b601b197aa5cd735d9b5edf08dd10140ace5372eec5c1d4094eb9764"`
Dec 05 19:11:08.316 INFO [stdout] e2f8ca46b601b197aa5cd735d9b5edf08dd10140ace5372eec5c1d4094eb9764
Dec 05 19:11:08.318 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/pr-56514/worker-5/master#906deae0790bd18681b937fe9a141a3c26cf1855:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-5/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 19:11:08.464 INFO [stdout] 60bdc7428fa9a9abcfbbccb02efd626909e57d346c956ea0096177e08ac26f24
Dec 05 19:11:08.465 INFO running `"docker" "start" "-a" "60bdc7428fa9a9abcfbbccb02efd626909e57d346c956ea0096177e08ac26f24"`
Dec 05 19:11:08.900 INFO [stderr] usermod: no changes
Dec 05 19:11:08.925 INFO [stderr] warning: An explicit [[bin]] section is specified in Cargo.toml which currently
Dec 05 19:11:08.925 INFO [stderr] disables Cargo from automatically inferring other binary targets.
Dec 05 19:11:08.925 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following
Dec 05 19:11:08.925 INFO [stderr] files will be included as a binary target:
Dec 05 19:11:08.925 INFO [stderr] 
Dec 05 19:11:08.925 INFO [stderr] * /source/src/main.rs
Dec 05 19:11:08.925 INFO [stderr] 
Dec 05 19:11:08.925 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be
Dec 05 19:11:08.925 INFO [stderr] ready to be compiled as a binary target today. You can future-proof yourself
Dec 05 19:11:08.925 INFO [stderr] and disable this warning by adding `autobins = false` to your [package]
Dec 05 19:11:08.925 INFO [stderr] section. You may also move the files to a location where Cargo would not
Dec 05 19:11:08.925 INFO [stderr] automatically infer them to be a target, such as in subfolders.
Dec 05 19:11:08.925 INFO [stderr] 
Dec 05 19:11:08.925 INFO [stderr] For more information on this warning you can consult
Dec 05 19:11:08.925 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330
Dec 05 19:11:09.010 INFO [stderr]    Compiling rust-json v0.1.0 (/source)
Dec 05 19:11:10.494 INFO [stderr]     Finished dev [unoptimized + debuginfo] target(s) in 1.57s
Dec 05 19:11:10.504 INFO [stderr] su: No module specific data is present
Dec 05 19:11:10.719 INFO running `"docker" "inspect" "60bdc7428fa9a9abcfbbccb02efd626909e57d346c956ea0096177e08ac26f24"`
Dec 05 19:11:10.790 INFO running `"docker" "rm" "-f" "60bdc7428fa9a9abcfbbccb02efd626909e57d346c956ea0096177e08ac26f24"`
Dec 05 19:11:10.859 INFO [stdout] 60bdc7428fa9a9abcfbbccb02efd626909e57d346c956ea0096177e08ac26f24
Dec 05 19:11:10.862 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/pr-56514/worker-5/master#906deae0790bd18681b937fe9a141a3c26cf1855:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-5/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 19:11:11.015 INFO [stdout] cfc19ff41a32e7adca6e7850ee69c550b64dcdb9330714898be470af5350f048
Dec 05 19:11:11.017 INFO running `"docker" "start" "-a" "cfc19ff41a32e7adca6e7850ee69c550b64dcdb9330714898be470af5350f048"`
Dec 05 19:11:11.430 INFO [stderr] usermod: no changes
Dec 05 19:11:11.454 INFO [stderr] warning: An explicit [[bin]] section is specified in Cargo.toml which currently
Dec 05 19:11:11.454 INFO [stderr] disables Cargo from automatically inferring other binary targets.
Dec 05 19:11:11.454 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following
Dec 05 19:11:11.454 INFO [stderr] files will be included as a binary target:
Dec 05 19:11:11.454 INFO [stderr] 
Dec 05 19:11:11.454 INFO [stderr] * /source/src/main.rs
Dec 05 19:11:11.454 INFO [stderr] 
Dec 05 19:11:11.454 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be
Dec 05 19:11:11.454 INFO [stderr] ready to be compiled as a binary target today. You can future-proof yourself
Dec 05 19:11:11.454 INFO [stderr] and disable this warning by adding `autobins = false` to your [package]
Dec 05 19:11:11.454 INFO [stderr] section. You may also move the files to a location where Cargo would not
Dec 05 19:11:11.454 INFO [stderr] automatically infer them to be a target, such as in subfolders.
Dec 05 19:11:11.454 INFO [stderr] 
Dec 05 19:11:11.454 INFO [stderr] For more information on this warning you can consult
Dec 05 19:11:11.454 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330
Dec 05 19:11:11.548 INFO [stderr]     Finished dev [unoptimized + debuginfo] target(s) in 0.10s
Dec 05 19:11:11.552 INFO [stderr]      Running /target/debug/deps/specialized-ae7f83f5343b9dbe
Dec 05 19:11:11.556 INFO [stdout] 
Dec 05 19:11:11.556 INFO [stdout] running 0 tests
Dec 05 19:11:11.556 INFO [stdout] 
Dec 05 19:11:11.556 INFO [stdout] test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out
Dec 05 19:11:11.556 INFO [stdout] 
Dec 05 19:11:11.556 INFO [stderr]      Running /target/debug/deps/unspecialized-9b83c7b0b97baf3a
Dec 05 19:11:11.557 INFO [stdout] 
Dec 05 19:11:11.557 INFO [stdout] running 0 tests
Dec 05 19:11:11.557 INFO [stdout] 
Dec 05 19:11:11.557 INFO [stdout] test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out
Dec 05 19:11:11.557 INFO [stdout] 
Dec 05 19:11:11.561 INFO [stderr] su: No module specific data is present
Dec 05 19:11:11.788 INFO running `"docker" "inspect" "cfc19ff41a32e7adca6e7850ee69c550b64dcdb9330714898be470af5350f048"`
Dec 05 19:11:11.850 INFO running `"docker" "rm" "-f" "cfc19ff41a32e7adca6e7850ee69c550b64dcdb9330714898be470af5350f048"`
Dec 05 19:11:11.947 INFO [stdout] cfc19ff41a32e7adca6e7850ee69c550b64dcdb9330714898be470af5350f048