[INFO] updating cached repository razvan-panda/rust-spoj
[INFO] running `"git" "fetch" "--all"`
[INFO] [stdout] Fetching origin
[INFO] [stderr] From git://github.com/razvan-panda/rust-spoj
[INFO] [stderr]  * branch            HEAD       -> FETCH_HEAD
[INFO] running `"git" "clone" "work/cache/sources/gh/razvan-panda/rust-spoj" "work/ex/beta-1.37-6/sources/1.36.0/gh/razvan-panda/rust-spoj"`
[INFO] [stderr] Cloning into 'work/ex/beta-1.37-6/sources/1.36.0/gh/razvan-panda/rust-spoj'...
[INFO] [stderr] done.
[INFO] running `"git" "clone" "work/cache/sources/gh/razvan-panda/rust-spoj" "work/ex/beta-1.37-6/sources/beta-2019-07-23/gh/razvan-panda/rust-spoj"`
[INFO] [stderr] Cloning into 'work/ex/beta-1.37-6/sources/beta-2019-07-23/gh/razvan-panda/rust-spoj'...
[INFO] [stderr] done.
[INFO] running `"git" "rev-parse" "HEAD"`
[INFO] [stdout] 0d7981031a1d87a76c46b99d1d5a0e30a27a57a9
[INFO] sha for GitHub repo razvan-panda/rust-spoj: 0d7981031a1d87a76c46b99d1d5a0e30a27a57a9
[INFO] validating manifest of razvan-panda/rust-spoj on toolchain 1.36.0
[INFO] running `"/mnt/big/crater/work/local/cargo-home/bin/cargo" "+1.36.0" "read-manifest" "--manifest-path" "Cargo.toml"`
[INFO] validating manifest of razvan-panda/rust-spoj on toolchain beta-2019-07-23
[INFO] running `"/mnt/big/crater/work/local/cargo-home/bin/cargo" "+beta-2019-07-23" "read-manifest" "--manifest-path" "Cargo.toml"`
[INFO] started frobbing razvan-panda/rust-spoj
[INFO] finished frobbing razvan-panda/rust-spoj
[INFO] frobbed toml for razvan-panda/rust-spoj written to work/ex/beta-1.37-6/sources/1.36.0/gh/razvan-panda/rust-spoj/Cargo.toml
[INFO] started frobbing razvan-panda/rust-spoj
[INFO] finished frobbing razvan-panda/rust-spoj
[INFO] frobbed toml for razvan-panda/rust-spoj written to work/ex/beta-1.37-6/sources/beta-2019-07-23/gh/razvan-panda/rust-spoj/Cargo.toml
[INFO] crate razvan-panda/rust-spoj already has a lockfile, it will not be regenerated
[INFO] running `"/mnt/big/crater/work/local/cargo-home/bin/cargo" "+1.36.0" "fetch" "--locked" "--manifest-path" "Cargo.toml"`
[INFO] running `"/mnt/big/crater/work/local/cargo-home/bin/cargo" "+beta-2019-07-23" "fetch" "--locked" "--manifest-path" "Cargo.toml"`
[INFO] testing razvan-panda/rust-spoj against 1.36.0 for beta-1.37-6
[INFO] running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/beta-1.37-6/worker-6/1.36.0:/opt/crater/target:rw,Z" "-v" "/mnt/big/crater/work/ex/beta-1.37-6/sources/1.36.0/gh/razvan-panda/rust-spoj:/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.36.0" "build" "--frozen"`
[INFO] [stdout] fa15afd1d53d9f993ec0250b0d382402aa4600fc361083595a75ac25c68f3460
[INFO] running `"docker" "start" "-a" "fa15afd1d53d9f993ec0250b0d382402aa4600fc361083595a75ac25c68f3460"`
[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] warning: path `/opt/crater/workdir/src/main.rs` was erroneously implicitly accepted for binary `hello_world`,
[INFO] [stderr] please set bin.path in Cargo.toml
[INFO] [stderr]    Compiling RustSPOJ v0.0.1 (/opt/crater/workdir)
[INFO] [stderr]     Finished dev [unoptimized + debuginfo] target(s) in 0.86s
[INFO] running `"docker" "inspect" "fa15afd1d53d9f993ec0250b0d382402aa4600fc361083595a75ac25c68f3460"`
[INFO] running `"docker" "rm" "-f" "fa15afd1d53d9f993ec0250b0d382402aa4600fc361083595a75ac25c68f3460"`
[INFO] [stdout] fa15afd1d53d9f993ec0250b0d382402aa4600fc361083595a75ac25c68f3460
[INFO] running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/beta-1.37-6/worker-6/1.36.0:/opt/crater/target:rw,Z" "-v" "/mnt/big/crater/work/ex/beta-1.37-6/sources/1.36.0/gh/razvan-panda/rust-spoj:/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.36.0" "test" "--frozen" "--no-run"`
[INFO] [stdout] 29f22fb5a4412dbc184a95cb7a158cec1adf6527006ddd5938cd1c3d80984347
[INFO] running `"docker" "start" "-a" "29f22fb5a4412dbc184a95cb7a158cec1adf6527006ddd5938cd1c3d80984347"`
[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] warning: path `/opt/crater/workdir/src/main.rs` was erroneously implicitly accepted for binary `hello_world`,
[INFO] [stderr] please set bin.path in Cargo.toml
[INFO] [stderr]     Blocking waiting for file lock on package cache lock
[INFO] [stderr]    Compiling RustSPOJ v0.0.1 (/opt/crater/workdir)
[INFO] [stderr]     Finished dev [unoptimized + debuginfo] target(s) in 1.56s
[INFO] running `"docker" "inspect" "29f22fb5a4412dbc184a95cb7a158cec1adf6527006ddd5938cd1c3d80984347"`
[INFO] running `"docker" "rm" "-f" "29f22fb5a4412dbc184a95cb7a158cec1adf6527006ddd5938cd1c3d80984347"`
[INFO] [stdout] 29f22fb5a4412dbc184a95cb7a158cec1adf6527006ddd5938cd1c3d80984347
[INFO] running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/beta-1.37-6/worker-6/1.36.0:/opt/crater/target:rw,Z" "-v" "/mnt/big/crater/work/ex/beta-1.37-6/sources/1.36.0/gh/razvan-panda/rust-spoj:/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.36.0" "test" "--frozen"`
[INFO] [stdout] a9f4087210a218c6eabd3260dfe868682d0385cb430ae8977c5ccdde6b5fe3ac
[INFO] running `"docker" "start" "-a" "a9f4087210a218c6eabd3260dfe868682d0385cb430ae8977c5ccdde6b5fe3ac"`
[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] warning: path `/opt/crater/workdir/src/main.rs` was erroneously implicitly accepted for binary `hello_world`,
[INFO] [stderr] please set bin.path in Cargo.toml
[INFO] [stderr]     Finished dev [unoptimized + debuginfo] target(s) in 0.02s
[INFO] [stderr]      Running /opt/crater/target/debug/deps/hello_world-4c324b4dfa57b69c
[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" "a9f4087210a218c6eabd3260dfe868682d0385cb430ae8977c5ccdde6b5fe3ac"`
[INFO] running `"docker" "rm" "-f" "a9f4087210a218c6eabd3260dfe868682d0385cb430ae8977c5ccdde6b5fe3ac"`
[INFO] [stdout] a9f4087210a218c6eabd3260dfe868682d0385cb430ae8977c5ccdde6b5fe3ac