[INFO] updating cached repository cisco/lal-build-manager
[INFO] running `"git" "fetch" "--all"`
[INFO] [stdout] Fetching origin
[INFO] [stderr] From git://github.com/cisco/lal-build-manager
[INFO] [stderr]  * branch              HEAD       -> FETCH_HEAD
[INFO] running `"git" "clone" "work/cache/sources/gh/cisco/lal-build-manager" "work/ex/pr-57967/sources/master#c1c3c4e95b69dfeaca5c5db6c622d7f90ad30a54/gh/cisco/lal-build-manager"`
[INFO] [stderr] Cloning into 'work/ex/pr-57967/sources/master#c1c3c4e95b69dfeaca5c5db6c622d7f90ad30a54/gh/cisco/lal-build-manager'...
[INFO] [stderr] done.
[INFO] running `"git" "clone" "work/cache/sources/gh/cisco/lal-build-manager" "work/ex/pr-57967/sources/try#7fea0229842e79db1159ea58ad9a653b288efee9/gh/cisco/lal-build-manager"`
[INFO] [stderr] Cloning into 'work/ex/pr-57967/sources/try#7fea0229842e79db1159ea58ad9a653b288efee9/gh/cisco/lal-build-manager'...
[INFO] [stderr] done.
[INFO] running `"git" "rev-parse" "HEAD"`
[INFO] [stdout] bb5c44883cfbfab1b1cc18913d638d055b2b8bec
[INFO] sha for GitHub repo cisco/lal-build-manager: bb5c44883cfbfab1b1cc18913d638d055b2b8bec
[INFO] validating manifest of cisco/lal-build-manager on toolchain master#c1c3c4e95b69dfeaca5c5db6c622d7f90ad30a54
[INFO] running `"/mnt/big/crater/work/local/cargo-home/bin/cargo" "+c1c3c4e95b69dfeaca5c5db6c622d7f90ad30a54-alt" "read-manifest" "--manifest-path" "Cargo.toml"`
[INFO] validating manifest of cisco/lal-build-manager on toolchain try#7fea0229842e79db1159ea58ad9a653b288efee9
[INFO] running `"/mnt/big/crater/work/local/cargo-home/bin/cargo" "+7fea0229842e79db1159ea58ad9a653b288efee9-alt" "read-manifest" "--manifest-path" "Cargo.toml"`
[INFO] started frobbing cisco/lal-build-manager
[INFO] removed 1 missing tests
[INFO] finished frobbing cisco/lal-build-manager
[INFO] frobbed toml for cisco/lal-build-manager written to work/ex/pr-57967/sources/master#c1c3c4e95b69dfeaca5c5db6c622d7f90ad30a54/gh/cisco/lal-build-manager/Cargo.toml
[INFO] started frobbing cisco/lal-build-manager
[INFO] removed 1 missing tests
[INFO] finished frobbing cisco/lal-build-manager
[INFO] frobbed toml for cisco/lal-build-manager written to work/ex/pr-57967/sources/try#7fea0229842e79db1159ea58ad9a653b288efee9/gh/cisco/lal-build-manager/Cargo.toml
[INFO] crate cisco/lal-build-manager has a lockfile. skipping
[INFO] running `"/mnt/big/crater/work/local/cargo-home/bin/cargo" "+c1c3c4e95b69dfeaca5c5db6c622d7f90ad30a54-alt" "fetch" "--locked" "--manifest-path" "Cargo.toml"`
[INFO] running `"/mnt/big/crater/work/local/cargo-home/bin/cargo" "+7fea0229842e79db1159ea58ad9a653b288efee9-alt" "fetch" "--locked" "--manifest-path" "Cargo.toml"`
[INFO] building cisco/lal-build-manager against master#c1c3c4e95b69dfeaca5c5db6c622d7f90ad30a54 for pr-57967
[INFO] running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/pr-57967/worker-1/master#c1c3c4e95b69dfeaca5c5db6c622d7f90ad30a54:/opt/crater/target:rw,Z" "-v" "/mnt/big/crater/work/ex/pr-57967/sources/master#c1c3c4e95b69dfeaca5c5db6c622d7f90ad30a54/gh/cisco/lal-build-manager:/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=forbid" "-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" "+c1c3c4e95b69dfeaca5c5db6c622d7f90ad30a54-alt" "build" "--frozen"`
[INFO] [stdout] cb304921c489c5de2a29b2cecb03984f0a758768a570b0b02e736914cc0bb1a4
[INFO] running `"docker" "start" "-a" "cb304921c489c5de2a29b2cecb03984f0a758768a570b0b02e736914cc0bb1a4"`
[INFO] [stderr] warning: An explicit [[test]] section is specified in Cargo.toml which currently
[INFO] [stderr] disables Cargo from automatically inferring other test targets.
[INFO] [stderr] This inference behavior will change in the Rust 2018 edition and the following
[INFO] [stderr] files will be included as a test target:
[INFO] [stderr] 
[INFO] [stderr] * /opt/crater/workdir/tests/testmain.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 test target today. You can future-proof yourself
[INFO] [stderr] and disable this warning by adding `autotests = 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 smallvec v0.3.3
[INFO] [stderr]    Compiling sha1 v0.3.0
[INFO] [stderr]    Compiling ansi_term v0.7.5
[INFO] [stderr]    Compiling xattr v0.1.11
[INFO] [stderr]    Compiling clicolors-control v0.1.0
[INFO] [stderr]    Compiling serde_json v1.0.8
[INFO] [stderr]    Compiling loggerv v0.6.0
[INFO] [stderr]    Compiling clap v2.27.1
[INFO] [stderr]    Compiling parking_lot_core v0.2.1
[INFO] [stderr]    Compiling chrono v0.2.25
[INFO] [stderr]    Compiling tar v0.4.11
[INFO] [stderr]    Compiling parking_lot v0.4.0
[INFO] [stderr]    Compiling indicatif v0.3.3
[INFO] [stderr]    Compiling lal v3.8.1 (/opt/crater/workdir)
[INFO] [stderr] warning: use of deprecated item 'std::env::home_dir': This function's behavior is unexpected and probably not what you want. Consider using the home_dir function from https://crates.io/crates/dirs instead.
[INFO] [stderr]   --> src/core/config.rs:18:9
[INFO] [stderr]    |
[INFO] [stderr] 18 |         env::home_dir().unwrap()
[INFO] [stderr]    |         ^^^^^^^^^^^^^
[INFO] [stderr]    |
[INFO] [stderr]    = note: #[warn(deprecated)] on by default
[INFO] [stderr] 
[INFO] [stderr] warning: use of deprecated item 'std::env::home_dir': This function's behavior is unexpected and probably not what you want. Consider using the home_dir function from https://crates.io/crates/dirs instead.
[INFO] [stderr]    --> src/shell.rs:197:16
[INFO] [stderr]     |
[INFO] [stderr] 197 |     let home = env::home_dir().unwrap(); // crash if no $HOME
[INFO] [stderr]     |                ^^^^^^^^^^^^^
[INFO] [stderr] 
[INFO] [stderr]     Finished dev [unoptimized + debuginfo] target(s) in 48.06s
[INFO] running `"docker" "inspect" "cb304921c489c5de2a29b2cecb03984f0a758768a570b0b02e736914cc0bb1a4"`
[INFO] running `"docker" "rm" "-f" "cb304921c489c5de2a29b2cecb03984f0a758768a570b0b02e736914cc0bb1a4"`
[INFO] [stdout] cb304921c489c5de2a29b2cecb03984f0a758768a570b0b02e736914cc0bb1a4
[INFO] running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/pr-57967/worker-1/master#c1c3c4e95b69dfeaca5c5db6c622d7f90ad30a54:/opt/crater/target:rw,Z" "-v" "/mnt/big/crater/work/ex/pr-57967/sources/master#c1c3c4e95b69dfeaca5c5db6c622d7f90ad30a54/gh/cisco/lal-build-manager:/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=forbid" "-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" "+c1c3c4e95b69dfeaca5c5db6c622d7f90ad30a54-alt" "test" "--frozen" "--no-run"`
[INFO] [stdout] 8fe901f98d2c7086e619a37df6752f57b6ef665276bcfe41d8413a44ae060b6d
[INFO] running `"docker" "start" "-a" "8fe901f98d2c7086e619a37df6752f57b6ef665276bcfe41d8413a44ae060b6d"`
[INFO] [stderr] warning: An explicit [[test]] section is specified in Cargo.toml which currently
[INFO] [stderr] disables Cargo from automatically inferring other test targets.
[INFO] [stderr] This inference behavior will change in the Rust 2018 edition and the following
[INFO] [stderr] files will be included as a test target:
[INFO] [stderr] 
[INFO] [stderr] * /opt/crater/workdir/tests/testmain.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 test target today. You can future-proof yourself
[INFO] [stderr] and disable this warning by adding `autotests = 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 lal v3.8.1 (/opt/crater/workdir)
[INFO] [stderr] warning: use of deprecated item 'std::env::home_dir': This function's behavior is unexpected and probably not what you want. Consider using the home_dir function from https://crates.io/crates/dirs instead.
[INFO] [stderr]   --> src/core/config.rs:18:9
[INFO] [stderr]    |
[INFO] [stderr] 18 |         env::home_dir().unwrap()
[INFO] [stderr]    |         ^^^^^^^^^^^^^
[INFO] [stderr]    |
[INFO] [stderr]    = note: #[warn(deprecated)] on by default
[INFO] [stderr] 
[INFO] [stderr] warning: use of deprecated item 'std::env::home_dir': This function's behavior is unexpected and probably not what you want. Consider using the home_dir function from https://crates.io/crates/dirs instead.
[INFO] [stderr]    --> src/shell.rs:197:16
[INFO] [stderr]     |
[INFO] [stderr] 197 |     let home = env::home_dir().unwrap(); // crash if no $HOME
[INFO] [stderr]     |                ^^^^^^^^^^^^^
[INFO] [stderr] 
[INFO] [stderr]     Finished dev [unoptimized + debuginfo] target(s) in 4.86s
[INFO] running `"docker" "inspect" "8fe901f98d2c7086e619a37df6752f57b6ef665276bcfe41d8413a44ae060b6d"`
[INFO] running `"docker" "rm" "-f" "8fe901f98d2c7086e619a37df6752f57b6ef665276bcfe41d8413a44ae060b6d"`
[INFO] [stdout] 8fe901f98d2c7086e619a37df6752f57b6ef665276bcfe41d8413a44ae060b6d