Dec 05 19:10:49.135 INFO testing juli1/rust-json-example against try#6eb0fd3ac58f9b16bddb9924a17c3b6c156aa468 for pr-56514
Dec 05 19:10:49.135 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/pr-56514/worker-4/try#6eb0fd3ac58f9b16bddb9924a17c3b6c156aa468:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-4/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 19:10:49.433 INFO [stdout] f34fa6f1b3728f2f8eba7c388b39a30365962742e4cf972efef71de823f35902
Dec 05 19:10:49.440 INFO running `"docker" "start" "-a" "f34fa6f1b3728f2f8eba7c388b39a30365962742e4cf972efef71de823f35902"`
Dec 05 19:10:50.092 INFO [stderr] usermod: no changes
Dec 05 19:10:50.116 INFO [stderr] warning: An explicit [[bin]] section is specified in Cargo.toml which currently
Dec 05 19:10:50.116 INFO [stderr] disables Cargo from automatically inferring other binary targets.
Dec 05 19:10:50.116 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following
Dec 05 19:10:50.116 INFO [stderr] files will be included as a binary target:
Dec 05 19:10:50.116 INFO [stderr] 
Dec 05 19:10:50.116 INFO [stderr] * /source/src/main.rs
Dec 05 19:10:50.116 INFO [stderr] 
Dec 05 19:10:50.116 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be
Dec 05 19:10:50.116 INFO [stderr] ready to be compiled as a binary target today. You can future-proof yourself
Dec 05 19:10:50.116 INFO [stderr] and disable this warning by adding `autobins = false` to your [package]
Dec 05 19:10:50.116 INFO [stderr] section. You may also move the files to a location where Cargo would not
Dec 05 19:10:50.116 INFO [stderr] automatically infer them to be a target, such as in subfolders.
Dec 05 19:10:50.116 INFO [stderr] 
Dec 05 19:10:50.116 INFO [stderr] For more information on this warning you can consult
Dec 05 19:10:50.116 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330
Dec 05 19:10:50.268 INFO [stderr]    Compiling relay v0.1.1
Dec 05 19:10:50.268 INFO [stderr]    Compiling futures-cpupool v0.1.8
Dec 05 19:10:50.269 INFO [stderr]    Compiling http v0.1.4
Dec 05 19:10:50.269 INFO [stderr]    Compiling tokio-tls v0.1.4
Dec 05 19:10:51.425 INFO [stderr]    Compiling hyper v0.11.16
Dec 05 19:10:59.279 INFO [stderr]    Compiling hyper-tls v0.1.2
Dec 05 19:11:00.562 INFO [stderr]    Compiling rust-json v0.1.0 (/source)
Dec 05 19:11:05.492 INFO [stderr]     Finished dev [unoptimized + debuginfo] target(s) in 15.37s
Dec 05 19:11:05.492 INFO [stderr] su: No module specific data is present
Dec 05 19:11:06.063 INFO running `"docker" "inspect" "f34fa6f1b3728f2f8eba7c388b39a30365962742e4cf972efef71de823f35902"`
Dec 05 19:11:06.193 INFO running `"docker" "rm" "-f" "f34fa6f1b3728f2f8eba7c388b39a30365962742e4cf972efef71de823f35902"`
Dec 05 19:11:06.293 INFO [stdout] f34fa6f1b3728f2f8eba7c388b39a30365962742e4cf972efef71de823f35902
Dec 05 19:11:06.298 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/pr-56514/worker-4/try#6eb0fd3ac58f9b16bddb9924a17c3b6c156aa468:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-4/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 19:11:06.450 INFO [stdout] 7c45ca3b0f325fbc5d3c8d1201e57b88b946eb7340376d6a9fd4c32d77d41d5e
Dec 05 19:11:06.452 INFO running `"docker" "start" "-a" "7c45ca3b0f325fbc5d3c8d1201e57b88b946eb7340376d6a9fd4c32d77d41d5e"`
Dec 05 19:11:06.896 INFO [stderr] usermod: no changes
Dec 05 19:11:06.926 INFO [stderr] warning: An explicit [[bin]] section is specified in Cargo.toml which currently
Dec 05 19:11:06.926 INFO [stderr] disables Cargo from automatically inferring other binary targets.
Dec 05 19:11:06.926 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following
Dec 05 19:11:06.926 INFO [stderr] files will be included as a binary target:
Dec 05 19:11:06.926 INFO [stderr] 
Dec 05 19:11:06.926 INFO [stderr] * /source/src/main.rs
Dec 05 19:11:06.926 INFO [stderr] 
Dec 05 19:11:06.926 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be
Dec 05 19:11:06.926 INFO [stderr] ready to be compiled as a binary target today. You can future-proof yourself
Dec 05 19:11:06.926 INFO [stderr] and disable this warning by adding `autobins = false` to your [package]
Dec 05 19:11:06.926 INFO [stderr] section. You may also move the files to a location where Cargo would not
Dec 05 19:11:06.926 INFO [stderr] automatically infer them to be a target, such as in subfolders.
Dec 05 19:11:06.926 INFO [stderr] 
Dec 05 19:11:06.926 INFO [stderr] For more information on this warning you can consult
Dec 05 19:11:06.926 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330
Dec 05 19:11:07.019 INFO [stderr]    Compiling rust-json v0.1.0 (/source)
Dec 05 19:11:08.579 INFO [stderr]     Finished dev [unoptimized + debuginfo] target(s) in 1.66s
Dec 05 19:11:08.589 INFO [stderr] su: No module specific data is present
Dec 05 19:11:08.781 INFO running `"docker" "inspect" "7c45ca3b0f325fbc5d3c8d1201e57b88b946eb7340376d6a9fd4c32d77d41d5e"`
Dec 05 19:11:08.834 INFO running `"docker" "rm" "-f" "7c45ca3b0f325fbc5d3c8d1201e57b88b946eb7340376d6a9fd4c32d77d41d5e"`
Dec 05 19:11:08.904 INFO [stdout] 7c45ca3b0f325fbc5d3c8d1201e57b88b946eb7340376d6a9fd4c32d77d41d5e
Dec 05 19:11:08.910 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/pr-56514/worker-4/try#6eb0fd3ac58f9b16bddb9924a17c3b6c156aa468:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-4/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 19:11:09.077 INFO [stdout] df0b19a88078f49fb56a12266b4e8641a377d6da3890da5b57a4d47f78220c14
Dec 05 19:11:09.092 INFO running `"docker" "start" "-a" "df0b19a88078f49fb56a12266b4e8641a377d6da3890da5b57a4d47f78220c14"`
Dec 05 19:11:09.582 INFO [stderr] usermod: no changes
Dec 05 19:11:09.616 INFO [stderr] warning: An explicit [[bin]] section is specified in Cargo.toml which currently
Dec 05 19:11:09.616 INFO [stderr] disables Cargo from automatically inferring other binary targets.
Dec 05 19:11:09.616 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following
Dec 05 19:11:09.616 INFO [stderr] files will be included as a binary target:
Dec 05 19:11:09.616 INFO [stderr] 
Dec 05 19:11:09.616 INFO [stderr] * /source/src/main.rs
Dec 05 19:11:09.616 INFO [stderr] 
Dec 05 19:11:09.616 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be
Dec 05 19:11:09.616 INFO [stderr] ready to be compiled as a binary target today. You can future-proof yourself
Dec 05 19:11:09.616 INFO [stderr] and disable this warning by adding `autobins = false` to your [package]
Dec 05 19:11:09.616 INFO [stderr] section. You may also move the files to a location where Cargo would not
Dec 05 19:11:09.616 INFO [stderr] automatically infer them to be a target, such as in subfolders.
Dec 05 19:11:09.616 INFO [stderr] 
Dec 05 19:11:09.616 INFO [stderr] For more information on this warning you can consult
Dec 05 19:11:09.616 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330
Dec 05 19:11:09.695 INFO [stderr]     Finished dev [unoptimized + debuginfo] target(s) in 0.09s
Dec 05 19:11:09.698 INFO [stderr]      Running /target/debug/deps/specialized-cd827d45c74c409a
Dec 05 19:11:09.701 INFO [stdout] 
Dec 05 19:11:09.701 INFO [stdout] running 0 tests
Dec 05 19:11:09.701 INFO [stdout] 
Dec 05 19:11:09.701 INFO [stdout] test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out
Dec 05 19:11:09.701 INFO [stdout] 
Dec 05 19:11:09.701 INFO [stderr]      Running /target/debug/deps/unspecialized-af58e9dfbad92f7d
Dec 05 19:11:09.703 INFO [stdout] 
Dec 05 19:11:09.703 INFO [stdout] running 0 tests
Dec 05 19:11:09.703 INFO [stdout] 
Dec 05 19:11:09.703 INFO [stdout] test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out
Dec 05 19:11:09.703 INFO [stdout] 
Dec 05 19:11:09.705 INFO [stderr] su: No module specific data is present
Dec 05 19:11:10.007 INFO running `"docker" "inspect" "df0b19a88078f49fb56a12266b4e8641a377d6da3890da5b57a4d47f78220c14"`
Dec 05 19:11:10.086 INFO running `"docker" "rm" "-f" "df0b19a88078f49fb56a12266b4e8641a377d6da3890da5b57a4d47f78220c14"`
Dec 05 19:11:10.221 INFO [stdout] df0b19a88078f49fb56a12266b4e8641a377d6da3890da5b57a4d47f78220c14