Nov 16 23:05:32.557 INFO testing juli1/rust-json-example against try#2e026d6e5d7621634147ad4c8074f1d964dbb1be for pr-55982
Nov 16 23:05:32.557 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/pr-55982/worker-1/try#2e026d6e5d7621634147ad4c8074f1d964dbb1be:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-1/pr-55982/try#2e026d6e5d7621634147ad4c8074f1d964dbb1be:/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 +2e026d6e5d7621634147ad4c8074f1d964dbb1be-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"`
Nov 16 23:05:32.903 INFO [stdout] 6d9199418eab1e3352bfbeac06f3be6b9ab8d3f669a26a8616993295b94a3ca4
Nov 16 23:05:32.905 INFO running `"docker" "start" "-a" "6d9199418eab1e3352bfbeac06f3be6b9ab8d3f669a26a8616993295b94a3ca4"`
Nov 16 23:05:33.575 INFO [stderr] usermod: no changes
Nov 16 23:05:33.643 INFO [stderr] warning: An explicit [[bin]] section is specified in Cargo.toml which currently
Nov 16 23:05:33.643 INFO [stderr] disables Cargo from automatically inferring other binary targets.
Nov 16 23:05:33.643 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following
Nov 16 23:05:33.643 INFO [stderr] files will be included as a binary target:
Nov 16 23:05:33.643 INFO [stderr] 
Nov 16 23:05:33.643 INFO [stderr] * /source/src/main.rs
Nov 16 23:05:33.643 INFO [stderr] 
Nov 16 23:05:33.643 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be
Nov 16 23:05:33.643 INFO [stderr] ready to be compiled as a binary target today. You can future-proof yourself
Nov 16 23:05:33.643 INFO [stderr] and disable this warning by adding `autobins = false` to your [package]
Nov 16 23:05:33.643 INFO [stderr] section. You may also move the files to a location where Cargo would not
Nov 16 23:05:33.643 INFO [stderr] automatically infer them to be a target, such as in subfolders.
Nov 16 23:05:33.643 INFO [stderr] 
Nov 16 23:05:33.643 INFO [stderr] For more information on this warning you can consult
Nov 16 23:05:33.643 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330
Nov 16 23:05:33.816 INFO [stderr]    Compiling serde_json v1.0.9
Nov 16 23:05:33.816 INFO [stderr]    Compiling http v0.1.4
Nov 16 23:05:33.816 INFO [stderr]    Compiling mio v0.6.12
Nov 16 23:05:33.816 INFO [stderr]    Compiling tokio-io v0.1.4
Nov 16 23:05:38.206 INFO [stderr]    Compiling tokio-core v0.1.12
Nov 16 23:05:42.160 INFO [stderr]    Compiling tokio-proto v0.1.1
Nov 16 23:05:42.161 INFO [stderr]    Compiling tokio-tls v0.1.4
Nov 16 23:05:45.384 INFO [stderr]    Compiling hyper v0.11.16
Nov 16 23:05:52.455 INFO [stderr]    Compiling hyper-tls v0.1.2
Nov 16 23:05:53.638 INFO [stderr]    Compiling rust-json v0.1.0 (/source)
Nov 16 23:05:58.570 INFO [stderr]     Finished dev [unoptimized + debuginfo] target(s) in 24.97s
Nov 16 23:05:58.582 INFO [stderr] su: No module specific data is present
Nov 16 23:05:58.798 INFO running `"docker" "inspect" "6d9199418eab1e3352bfbeac06f3be6b9ab8d3f669a26a8616993295b94a3ca4"`
Nov 16 23:05:58.894 INFO running `"docker" "rm" "-f" "6d9199418eab1e3352bfbeac06f3be6b9ab8d3f669a26a8616993295b94a3ca4"`
Nov 16 23:05:59.024 INFO [stdout] 6d9199418eab1e3352bfbeac06f3be6b9ab8d3f669a26a8616993295b94a3ca4
Nov 16 23:05:59.032 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/pr-55982/worker-1/try#2e026d6e5d7621634147ad4c8074f1d964dbb1be:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-1/pr-55982/try#2e026d6e5d7621634147ad4c8074f1d964dbb1be:/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 +2e026d6e5d7621634147ad4c8074f1d964dbb1be-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"`
Nov 16 23:05:59.219 INFO [stdout] f242f18487a1b4dd62ed9adfe582e88312c07ae0b08670c917775e3cdf956b48
Nov 16 23:05:59.225 INFO running `"docker" "start" "-a" "f242f18487a1b4dd62ed9adfe582e88312c07ae0b08670c917775e3cdf956b48"`
Nov 16 23:05:59.662 INFO [stderr] usermod: no changes
Nov 16 23:05:59.687 INFO [stderr] warning: An explicit [[bin]] section is specified in Cargo.toml which currently
Nov 16 23:05:59.687 INFO [stderr] disables Cargo from automatically inferring other binary targets.
Nov 16 23:05:59.687 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following
Nov 16 23:05:59.687 INFO [stderr] files will be included as a binary target:
Nov 16 23:05:59.687 INFO [stderr] 
Nov 16 23:05:59.687 INFO [stderr] * /source/src/main.rs
Nov 16 23:05:59.687 INFO [stderr] 
Nov 16 23:05:59.687 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be
Nov 16 23:05:59.687 INFO [stderr] ready to be compiled as a binary target today. You can future-proof yourself
Nov 16 23:05:59.687 INFO [stderr] and disable this warning by adding `autobins = false` to your [package]
Nov 16 23:05:59.687 INFO [stderr] section. You may also move the files to a location where Cargo would not
Nov 16 23:05:59.687 INFO [stderr] automatically infer them to be a target, such as in subfolders.
Nov 16 23:05:59.687 INFO [stderr] 
Nov 16 23:05:59.687 INFO [stderr] For more information on this warning you can consult
Nov 16 23:05:59.687 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330
Nov 16 23:05:59.792 INFO [stderr]    Compiling rust-json v0.1.0 (/source)
Nov 16 23:06:01.299 INFO [stderr]     Finished dev [unoptimized + debuginfo] target(s) in 1.62s
Nov 16 23:06:01.310 INFO [stderr] su: No module specific data is present
Nov 16 23:06:01.572 INFO running `"docker" "inspect" "f242f18487a1b4dd62ed9adfe582e88312c07ae0b08670c917775e3cdf956b48"`
Nov 16 23:06:01.644 INFO running `"docker" "rm" "-f" "f242f18487a1b4dd62ed9adfe582e88312c07ae0b08670c917775e3cdf956b48"`
Nov 16 23:06:01.745 INFO [stdout] f242f18487a1b4dd62ed9adfe582e88312c07ae0b08670c917775e3cdf956b48
Nov 16 23:06:01.748 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/pr-55982/worker-1/try#2e026d6e5d7621634147ad4c8074f1d964dbb1be:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-1/pr-55982/try#2e026d6e5d7621634147ad4c8074f1d964dbb1be:/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 +2e026d6e5d7621634147ad4c8074f1d964dbb1be-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"`
Nov 16 23:06:01.924 INFO [stdout] 501b055d4a49c43f64da5fa0db7936cffd9755c3a1167b5a74b23e6b66f51859
Nov 16 23:06:01.927 INFO running `"docker" "start" "-a" "501b055d4a49c43f64da5fa0db7936cffd9755c3a1167b5a74b23e6b66f51859"`
Nov 16 23:06:02.372 INFO [stderr] usermod: no changes
Nov 16 23:06:02.395 INFO [stderr] warning: An explicit [[bin]] section is specified in Cargo.toml which currently
Nov 16 23:06:02.395 INFO [stderr] disables Cargo from automatically inferring other binary targets.
Nov 16 23:06:02.395 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following
Nov 16 23:06:02.395 INFO [stderr] files will be included as a binary target:
Nov 16 23:06:02.396 INFO [stderr] 
Nov 16 23:06:02.397 INFO [stderr] * /source/src/main.rs
Nov 16 23:06:02.397 INFO [stderr] 
Nov 16 23:06:02.397 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be
Nov 16 23:06:02.397 INFO [stderr] ready to be compiled as a binary target today. You can future-proof yourself
Nov 16 23:06:02.397 INFO [stderr] and disable this warning by adding `autobins = false` to your [package]
Nov 16 23:06:02.397 INFO [stderr] section. You may also move the files to a location where Cargo would not
Nov 16 23:06:02.397 INFO [stderr] automatically infer them to be a target, such as in subfolders.
Nov 16 23:06:02.397 INFO [stderr] 
Nov 16 23:06:02.397 INFO [stderr] For more information on this warning you can consult
Nov 16 23:06:02.397 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330
Nov 16 23:06:02.487 INFO [stderr]     Finished dev [unoptimized + debuginfo] target(s) in 0.10s
Nov 16 23:06:02.502 INFO [stderr]      Running /target/debug/deps/specialized-138b81cc2868e3c5
Nov 16 23:06:02.504 INFO [stdout] 
Nov 16 23:06:02.504 INFO [stdout] running 0 tests
Nov 16 23:06:02.504 INFO [stdout] 
Nov 16 23:06:02.504 INFO [stdout] test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out
Nov 16 23:06:02.504 INFO [stdout] 
Nov 16 23:06:02.504 INFO [stderr]      Running /target/debug/deps/unspecialized-0057a218fe36e721
Nov 16 23:06:02.505 INFO [stdout] 
Nov 16 23:06:02.506 INFO [stdout] running 0 tests
Nov 16 23:06:02.506 INFO [stdout] 
Nov 16 23:06:02.506 INFO [stdout] test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out
Nov 16 23:06:02.506 INFO [stdout] 
Nov 16 23:06:02.507 INFO [stderr] su: No module specific data is present
Nov 16 23:06:02.743 INFO running `"docker" "inspect" "501b055d4a49c43f64da5fa0db7936cffd9755c3a1167b5a74b23e6b66f51859"`
Nov 16 23:06:02.840 INFO running `"docker" "rm" "-f" "501b055d4a49c43f64da5fa0db7936cffd9755c3a1167b5a74b23e6b66f51859"`
Nov 16 23:06:02.958 INFO [stdout] 501b055d4a49c43f64da5fa0db7936cffd9755c3a1167b5a74b23e6b66f51859