[INFO] updating cached repository Fishrock123/nucleus-chakra
[INFO] running `"git" "fetch" "--all"`
[INFO] [stdout] Fetching origin
[INFO] [stderr] From git://github.com/Fishrock123/nucleus-chakra
[INFO] [stderr]  * branch            HEAD       -> FETCH_HEAD
[INFO] running `"git" "clone" "work/cache/sources/gh/Fishrock123/nucleus-chakra" "work/ex/beta-1.38-1/sources/1.37.0/gh/Fishrock123/nucleus-chakra"`
[INFO] [stderr] Cloning into 'work/ex/beta-1.38-1/sources/1.37.0/gh/Fishrock123/nucleus-chakra'...
[INFO] [stderr] done.
[INFO] running `"git" "clone" "work/cache/sources/gh/Fishrock123/nucleus-chakra" "work/ex/beta-1.38-1/sources/beta-2019-08-13/gh/Fishrock123/nucleus-chakra"`
[INFO] [stderr] Cloning into 'work/ex/beta-1.38-1/sources/beta-2019-08-13/gh/Fishrock123/nucleus-chakra'...
[INFO] [stderr] done.
[INFO] running `"git" "rev-parse" "HEAD"`
[INFO] [stdout] 90d4a5440cc43df0bb08fae2e3b972919b6bcae2
[INFO] sha for GitHub repo Fishrock123/nucleus-chakra: 90d4a5440cc43df0bb08fae2e3b972919b6bcae2
[INFO] validating manifest of Fishrock123/nucleus-chakra 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 Fishrock123/nucleus-chakra 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 Fishrock123/nucleus-chakra
[INFO] finished frobbing Fishrock123/nucleus-chakra
[INFO] frobbed toml for Fishrock123/nucleus-chakra written to work/ex/beta-1.38-1/sources/1.37.0/gh/Fishrock123/nucleus-chakra/Cargo.toml
[INFO] started frobbing Fishrock123/nucleus-chakra
[INFO] finished frobbing Fishrock123/nucleus-chakra
[INFO] frobbed toml for Fishrock123/nucleus-chakra written to work/ex/beta-1.38-1/sources/beta-2019-08-13/gh/Fishrock123/nucleus-chakra/Cargo.toml
[INFO] crate Fishrock123/nucleus-chakra 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] running `"/mnt/big/crater/work/local/cargo-home/bin/cargo" "+beta-2019-08-13" "fetch" "--locked" "--manifest-path" "Cargo.toml"`
[INFO] testing Fishrock123/nucleus-chakra against beta-2019-08-13 for beta-1.38-1
[INFO] running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/beta-1.38-1/worker-1/beta-2019-08-13:/opt/crater/target:rw,Z" "-v" "/mnt/big/crater/work/ex/beta-1.38-1/sources/beta-2019-08-13/gh/Fishrock123/nucleus-chakra:/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" "+beta-2019-08-13" "build" "--frozen"`
[INFO] [stdout] 34971a55f07e072233b254ac2c212978827e174d7ca28a7bd9a54fd8ee4959d5
[INFO] running `"docker" "start" "-a" "34971a55f07e072233b254ac2c212978827e174d7ca28a7bd9a54fd8ee4959d5"`
[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/nucleus.rs` was erroneously implicitly accepted for binary `nucleus`,
[INFO] [stderr] please set bin.path in Cargo.toml
[INFO] [stderr]    Compiling gcc v0.3.32
[INFO] [stderr]    Compiling libc v0.2.15
[INFO] [stderr]    Compiling podio v0.1.5
[INFO] [stderr]    Compiling getopts v0.2.14
[INFO] [stderr] error[E0503]: cannot use `state` because it was mutably borrowed
[INFO] [stderr]     --> /opt/crater/cargo-home/registry/src/github.com-1ecc6299db9ec823/getopts-0.2.14/src/lib.rs:1008:33
[INFO] [stderr]      |
[INFO] [stderr] 955  |     let mut machine = |cont: &mut bool, (i, c): (usize, char)| {
[INFO] [stderr]      |                       ---------------------------------------- borrow of `state` occurs here
[INFO] [stderr] ...
[INFO] [stderr] 959  |         state = match (state, whitespace, limit) {
[INFO] [stderr]      |                        ----- borrow occurs due to use of `state` in closure
[INFO] [stderr] ...
[INFO] [stderr] 1008 |     while cont && match state { B | C => true, A => false } {
[INFO] [stderr]      |                                 ^ use of borrowed `state`
[INFO] [stderr] 1009 |         machine(&mut cont, (fake_i, ' '));
[INFO] [stderr]      |         ------- borrow later used here
[INFO] [stderr] 
[INFO] [stderr] error: aborting due to previous error
[INFO] [stderr] 
[INFO] [stderr] For more information about this error, try `rustc --explain E0503`.
[INFO] [stderr] error: Could not compile `getopts`.
[INFO] [stderr] warning: build failed, waiting for other jobs to finish...
[INFO] [stderr] error: build failed
[INFO] running `"docker" "inspect" "34971a55f07e072233b254ac2c212978827e174d7ca28a7bd9a54fd8ee4959d5"`
[INFO] running `"docker" "rm" "-f" "34971a55f07e072233b254ac2c212978827e174d7ca28a7bd9a54fd8ee4959d5"`
[INFO] [stdout] 34971a55f07e072233b254ac2c212978827e174d7ca28a7bd9a54fd8ee4959d5