[INFO] updating cached repository juli1/rust-json-example
[INFO] running `"git" "fetch" "--all"`
[INFO] [stdout] Fetching origin
[INFO] [stderr] From git://github.com/juli1/rust-json-example
[INFO] [stderr]  * branch            HEAD       -> FETCH_HEAD
[INFO] running `"git" "clone" "work/cache/sources/gh/juli1/rust-json-example" "work/ex/beta-1.38-1/sources/1.37.0/gh/juli1/rust-json-example"`
[INFO] [stderr] Cloning into 'work/ex/beta-1.38-1/sources/1.37.0/gh/juli1/rust-json-example'...
[INFO] [stderr] done.
[INFO] running `"git" "clone" "work/cache/sources/gh/juli1/rust-json-example" "work/ex/beta-1.38-1/sources/beta-2019-08-13/gh/juli1/rust-json-example"`
[INFO] [stderr] Cloning into 'work/ex/beta-1.38-1/sources/beta-2019-08-13/gh/juli1/rust-json-example'...
[INFO] [stderr] done.
[INFO] running `"git" "rev-parse" "HEAD"`
[INFO] [stdout] bf8c7b96349598177774fba4b87e4ffa23e215b2
[INFO] sha for GitHub repo juli1/rust-json-example: bf8c7b96349598177774fba4b87e4ffa23e215b2
[INFO] validating manifest of juli1/rust-json-example on toolchain 1.37.0
[INFO] running `"/mnt/big/crater/work/local/cargo-home/bin/cargo" "+1.37.0" "read-manifest" "--manifest-path" "Cargo.toml"`
[INFO] validating manifest of juli1/rust-json-example on toolchain beta-2019-08-13
[INFO] running `"/mnt/big/crater/work/local/cargo-home/bin/cargo" "+beta-2019-08-13" "read-manifest" "--manifest-path" "Cargo.toml"`
[INFO] started frobbing juli1/rust-json-example
[INFO] finished frobbing juli1/rust-json-example
[INFO] frobbed toml for juli1/rust-json-example written to work/ex/beta-1.38-1/sources/1.37.0/gh/juli1/rust-json-example/Cargo.toml
[INFO] started frobbing juli1/rust-json-example
[INFO] finished frobbing juli1/rust-json-example
[INFO] frobbed toml for juli1/rust-json-example written to work/ex/beta-1.38-1/sources/beta-2019-08-13/gh/juli1/rust-json-example/Cargo.toml
[INFO] crate juli1/rust-json-example already has a lockfile, it will not be regenerated
[INFO] running `"/mnt/big/crater/work/local/cargo-home/bin/cargo" "+1.37.0" "fetch" "--locked" "--manifest-path" "Cargo.toml"`
[INFO] [stderr]     Blocking waiting for file lock on package cache
[INFO] running `"/mnt/big/crater/work/local/cargo-home/bin/cargo" "+beta-2019-08-13" "fetch" "--locked" "--manifest-path" "Cargo.toml"`
[INFO] testing juli1/rust-json-example against 1.37.0 for beta-1.38-1
[INFO] running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/beta-1.38-1/worker-5/1.37.0:/opt/crater/target:rw,Z" "-v" "/mnt/big/crater/work/ex/beta-1.38-1/sources/1.37.0/gh/juli1/rust-json-example:/opt/crater/workdir:ro,Z" "-v" "/mnt/big/crater/work/local/cargo-home:/opt/crater/cargo-home:ro,Z" "-v" "/mnt/big/crater/work/local/rustup-home:/opt/crater/rustup-home:ro,Z" "-e" "USER_ID=1000" "-e" "SOURCE_DIR=/opt/crater/workdir" "-e" "MAP_USER_ID=1000" "-e" "CARGO_TARGET_DIR=/opt/crater/target" "-e" "CARGO_INCREMENTAL=0" "-e" "RUST_BACKTRACE=full" "-e" "RUSTFLAGS=--cap-lints=warn" "-e" "CARGO_HOME=/opt/crater/cargo-home" "-e" "RUSTUP_HOME=/opt/crater/rustup-home" "-w" "/opt/crater/workdir" "-m" "1536M" "--network" "none" "rustops/crates-build-env" "/opt/crater/cargo-home/bin/cargo" "+1.37.0" "build" "--frozen"`
[INFO] [stdout] 0d3d656f5e219ba41f17f12e61b36f4f82079ea4ff68da14c0a6e6d3ecb693f1
[INFO] running `"docker" "start" "-a" "0d3d656f5e219ba41f17f12e61b36f4f82079ea4ff68da14c0a6e6d3ecb693f1"`
[INFO] [stderr] warning: An explicit [[bin]] section is specified in Cargo.toml which currently
[INFO] [stderr] disables Cargo from automatically inferring other binary targets.
[INFO] [stderr] This inference behavior will change in the Rust 2018 edition and the following
[INFO] [stderr] files will be included as a binary target:
[INFO] [stderr] 
[INFO] [stderr] * /opt/crater/workdir/src/main.rs
[INFO] [stderr] 
[INFO] [stderr] This is likely to break cargo build or cargo test as these files may not be
[INFO] [stderr] ready to be compiled as a binary target today. You can future-proof yourself
[INFO] [stderr] and disable this warning by adding `autobins = false` to your [package]
[INFO] [stderr] section. You may also move the files to a location where Cargo would not
[INFO] [stderr] automatically infer them to be a target, such as in subfolders.
[INFO] [stderr] 
[INFO] [stderr] For more information on this warning you can consult
[INFO] [stderr] https://github.com/rust-lang/cargo/issues/5330
[INFO] [stderr]    Compiling tokio v0.0.0
[INFO] [stderr]    Compiling http v0.1.4
[INFO] [stderr]    Compiling native-tls v0.1.5
[INFO] [stderr]    Compiling tokio-proto v0.1.1
[INFO] [stderr]    Compiling tokio-tls v0.1.4
[INFO] [stderr]    Compiling hyper v0.11.16
[INFO] [stderr]    Compiling hyper-tls v0.1.2
[INFO] [stderr]    Compiling rust-json v0.1.0 (/opt/crater/workdir)
[INFO] [stderr]     Finished dev [unoptimized + debuginfo] target(s) in 23.02s
[INFO] running `"docker" "inspect" "0d3d656f5e219ba41f17f12e61b36f4f82079ea4ff68da14c0a6e6d3ecb693f1"`
[INFO] running `"docker" "rm" "-f" "0d3d656f5e219ba41f17f12e61b36f4f82079ea4ff68da14c0a6e6d3ecb693f1"`
[INFO] [stdout] 0d3d656f5e219ba41f17f12e61b36f4f82079ea4ff68da14c0a6e6d3ecb693f1
[INFO] running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/beta-1.38-1/worker-5/1.37.0:/opt/crater/target:rw,Z" "-v" "/mnt/big/crater/work/ex/beta-1.38-1/sources/1.37.0/gh/juli1/rust-json-example:/opt/crater/workdir:ro,Z" "-v" "/mnt/big/crater/work/local/cargo-home:/opt/crater/cargo-home:ro,Z" "-v" "/mnt/big/crater/work/local/rustup-home:/opt/crater/rustup-home:ro,Z" "-e" "USER_ID=1000" "-e" "SOURCE_DIR=/opt/crater/workdir" "-e" "MAP_USER_ID=1000" "-e" "CARGO_TARGET_DIR=/opt/crater/target" "-e" "CARGO_INCREMENTAL=0" "-e" "RUST_BACKTRACE=full" "-e" "RUSTFLAGS=--cap-lints=warn" "-e" "CARGO_HOME=/opt/crater/cargo-home" "-e" "RUSTUP_HOME=/opt/crater/rustup-home" "-w" "/opt/crater/workdir" "-m" "1536M" "--network" "none" "rustops/crates-build-env" "/opt/crater/cargo-home/bin/cargo" "+1.37.0" "test" "--frozen" "--no-run"`
[INFO] [stdout] f3dd1d1a50a2fc9c1063dae319402195f521f72ef2468cba26a54fa4c9c8f28b
[INFO] running `"docker" "start" "-a" "f3dd1d1a50a2fc9c1063dae319402195f521f72ef2468cba26a54fa4c9c8f28b"`
[INFO] [stderr] warning: An explicit [[bin]] section is specified in Cargo.toml which currently
[INFO] [stderr] disables Cargo from automatically inferring other binary targets.
[INFO] [stderr] This inference behavior will change in the Rust 2018 edition and the following
[INFO] [stderr] files will be included as a binary target:
[INFO] [stderr] 
[INFO] [stderr] * /opt/crater/workdir/src/main.rs
[INFO] [stderr] 
[INFO] [stderr] This is likely to break cargo build or cargo test as these files may not be
[INFO] [stderr] ready to be compiled as a binary target today. You can future-proof yourself
[INFO] [stderr] and disable this warning by adding `autobins = false` to your [package]
[INFO] [stderr] section. You may also move the files to a location where Cargo would not
[INFO] [stderr] automatically infer them to be a target, such as in subfolders.
[INFO] [stderr] 
[INFO] [stderr] For more information on this warning you can consult
[INFO] [stderr] https://github.com/rust-lang/cargo/issues/5330
[INFO] [stderr]    Compiling rust-json v0.1.0 (/opt/crater/workdir)
[INFO] [stderr]     Finished dev [unoptimized + debuginfo] target(s) in 0.85s
[INFO] running `"docker" "inspect" "f3dd1d1a50a2fc9c1063dae319402195f521f72ef2468cba26a54fa4c9c8f28b"`
[INFO] running `"docker" "rm" "-f" "f3dd1d1a50a2fc9c1063dae319402195f521f72ef2468cba26a54fa4c9c8f28b"`
[INFO] [stdout] f3dd1d1a50a2fc9c1063dae319402195f521f72ef2468cba26a54fa4c9c8f28b
[INFO] running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/beta-1.38-1/worker-5/1.37.0:/opt/crater/target:rw,Z" "-v" "/mnt/big/crater/work/ex/beta-1.38-1/sources/1.37.0/gh/juli1/rust-json-example:/opt/crater/workdir:ro,Z" "-v" "/mnt/big/crater/work/local/cargo-home:/opt/crater/cargo-home:ro,Z" "-v" "/mnt/big/crater/work/local/rustup-home:/opt/crater/rustup-home:ro,Z" "-e" "USER_ID=1000" "-e" "SOURCE_DIR=/opt/crater/workdir" "-e" "MAP_USER_ID=1000" "-e" "CARGO_TARGET_DIR=/opt/crater/target" "-e" "CARGO_INCREMENTAL=0" "-e" "RUST_BACKTRACE=full" "-e" "RUSTFLAGS=--cap-lints=warn" "-e" "CARGO_HOME=/opt/crater/cargo-home" "-e" "RUSTUP_HOME=/opt/crater/rustup-home" "-w" "/opt/crater/workdir" "-m" "1536M" "--network" "none" "rustops/crates-build-env" "/opt/crater/cargo-home/bin/cargo" "+1.37.0" "test" "--frozen"`
[INFO] [stdout] 4bd4008bad7172e7b864f036e899e0e43fd963b788eab07780066f515df41321
[INFO] running `"docker" "start" "-a" "4bd4008bad7172e7b864f036e899e0e43fd963b788eab07780066f515df41321"`
[INFO] [stderr] warning: An explicit [[bin]] section is specified in Cargo.toml which currently
[INFO] [stderr] disables Cargo from automatically inferring other binary targets.
[INFO] [stderr] This inference behavior will change in the Rust 2018 edition and the following
[INFO] [stderr] files will be included as a binary target:
[INFO] [stderr] 
[INFO] [stderr] * /opt/crater/workdir/src/main.rs
[INFO] [stderr] 
[INFO] [stderr] This is likely to break cargo build or cargo test as these files may not be
[INFO] [stderr] ready to be compiled as a binary target today. You can future-proof yourself
[INFO] [stderr] and disable this warning by adding `autobins = false` to your [package]
[INFO] [stderr] section. You may also move the files to a location where Cargo would not
[INFO] [stderr] automatically infer them to be a target, such as in subfolders.
[INFO] [stderr] 
[INFO] [stderr] For more information on this warning you can consult
[INFO] [stderr] https://github.com/rust-lang/cargo/issues/5330
[INFO] [stderr]     Finished dev [unoptimized + debuginfo] target(s) in 0.06s
[INFO] [stderr]      Running /opt/crater/target/debug/deps/specialized-20bd1dea9e3583eb
[INFO] [stderr]      Running /opt/crater/target/debug/deps/unspecialized-513eac25e0bb99b8
[INFO] [stdout] 
[INFO] [stdout] running 0 tests
[INFO] [stdout] 
[INFO] [stdout] test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] running 0 tests
[INFO] [stdout] 
[INFO] [stdout] test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out
[INFO] [stdout] 
[INFO] running `"docker" "inspect" "4bd4008bad7172e7b864f036e899e0e43fd963b788eab07780066f515df41321"`
[INFO] running `"docker" "rm" "-f" "4bd4008bad7172e7b864f036e899e0e43fd963b788eab07780066f515df41321"`
[INFO] [stdout] 4bd4008bad7172e7b864f036e899e0e43fd963b788eab07780066f515df41321