[INFO] crate libgitbox 0.1.0 is already in cache
[INFO] extracting crate libgitbox 0.1.0 into work/ex/pr-63376/sources/master#60960a260f7b5c695fd0717311d72ce62dd4eb43/reg/libgitbox/0.1.0
[INFO] extracting crate libgitbox 0.1.0 into work/ex/pr-63376/sources/try#266783e4e09e4e9d5307c1c8e695659c58bbcac7/reg/libgitbox/0.1.0
[INFO] validating manifest of libgitbox-0.1.0 on toolchain master#60960a260f7b5c695fd0717311d72ce62dd4eb43
[INFO] running `"/mnt/big/crater/work/local/cargo-home/bin/cargo" "+60960a260f7b5c695fd0717311d72ce62dd4eb43-alt" "read-manifest" "--manifest-path" "Cargo.toml"`
[INFO] validating manifest of libgitbox-0.1.0 on toolchain try#266783e4e09e4e9d5307c1c8e695659c58bbcac7
[INFO] running `"/mnt/big/crater/work/local/cargo-home/bin/cargo" "+266783e4e09e4e9d5307c1c8e695659c58bbcac7-alt" "read-manifest" "--manifest-path" "Cargo.toml"`
[INFO] started frobbing libgitbox-0.1.0
[INFO] removed 1 missing tests
[INFO] finished frobbing libgitbox-0.1.0
[INFO] frobbed toml for libgitbox-0.1.0 written to work/ex/pr-63376/sources/master#60960a260f7b5c695fd0717311d72ce62dd4eb43/reg/libgitbox/0.1.0/Cargo.toml
[INFO] started frobbing libgitbox-0.1.0
[INFO] removed 1 missing tests
[INFO] finished frobbing libgitbox-0.1.0
[INFO] frobbed toml for libgitbox-0.1.0 written to work/ex/pr-63376/sources/try#266783e4e09e4e9d5307c1c8e695659c58bbcac7/reg/libgitbox/0.1.0/Cargo.toml
[INFO] running `"/mnt/big/crater/work/local/cargo-home/bin/cargo" "+60960a260f7b5c695fd0717311d72ce62dd4eb43-alt" "generate-lockfile" "--manifest-path" "Cargo.toml" "-Zno-index-update"`
[INFO] running `"/mnt/big/crater/work/local/cargo-home/bin/cargo" "+266783e4e09e4e9d5307c1c8e695659c58bbcac7-alt" "generate-lockfile" "--manifest-path" "Cargo.toml" "-Zno-index-update"`
[INFO] running `"/mnt/big/crater/work/local/cargo-home/bin/cargo" "+60960a260f7b5c695fd0717311d72ce62dd4eb43-alt" "fetch" "--locked" "--manifest-path" "Cargo.toml"`
[INFO] running `"/mnt/big/crater/work/local/cargo-home/bin/cargo" "+266783e4e09e4e9d5307c1c8e695659c58bbcac7-alt" "fetch" "--locked" "--manifest-path" "Cargo.toml"`
[INFO] checking libgitbox-0.1.0 against try#266783e4e09e4e9d5307c1c8e695659c58bbcac7 for pr-63376
[INFO] running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/pr-63376/worker-5/try#266783e4e09e4e9d5307c1c8e695659c58bbcac7:/opt/crater/target:rw,Z" "-v" "/mnt/big/crater/work/ex/pr-63376/sources/try#266783e4e09e4e9d5307c1c8e695659c58bbcac7/reg/libgitbox/0.1.0:/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" "+266783e4e09e4e9d5307c1c8e695659c58bbcac7-alt" "check" "--frozen" "--all" "--all-targets"`
[INFO] [stdout] 173e8f03a162c9e9b51be293b66311d17f9ddad3c7fd3f4aecf9b0ba964fd04e
[INFO] running `"docker" "start" "-a" "173e8f03a162c9e9b51be293b66311d17f9ddad3c7fd3f4aecf9b0ba964fd04e"`
[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/all.rs
[INFO] [stderr] * /opt/crater/workdir/tests/base.rs
[INFO] [stderr] * /opt/crater/workdir/tests/config.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]     Checking mush v0.1.2
[INFO] [stderr]    Compiling num-traits v0.2.8
[INFO] [stderr]    Compiling num-integer v0.1.41
[INFO] [stderr]    Compiling chrono v0.4.7
[INFO] [stderr]    Compiling vergen v3.0.4
[INFO] [stderr]    Compiling libgitbox v0.1.0 (/opt/crater/workdir)
[INFO] [stderr] error[E0433]: failed to resolve: use of undeclared type or module `Flags`
[INFO] [stderr]  --> build.rs:7:21
[INFO] [stderr]   |
[INFO] [stderr] 7 |     let mut flags = Flags::all();
[INFO] [stderr]   |                     ^^^^^ use of undeclared type or module `Flags`
[INFO] [stderr] 
[INFO] [stderr] error[E0425]: cannot find value `NOW` in this scope
[INFO] [stderr]  --> build.rs:8:18
[INFO] [stderr]   |
[INFO] [stderr] 8 |     flags.toggle(NOW);
[INFO] [stderr]   |                  ^^^ not found in this scope
[INFO] [stderr] 
[INFO] [stderr] error[E0423]: expected function, found crate `vergen`
[INFO] [stderr]  --> build.rs:9:5
[INFO] [stderr]   |
[INFO] [stderr] 9 |     vergen(flags);
[INFO] [stderr]   |     ^^^^^^ not a function
[INFO] [stderr] 
[INFO] [stderr] warning: unused import: `vergen::*`
[INFO] [stderr]  --> build.rs:4:5
[INFO] [stderr]   |
[INFO] [stderr] 4 | use vergen::*;
[INFO] [stderr]   |     ^^^^^^^^^
[INFO] [stderr]   |
[INFO] [stderr]   = note: `#[warn(unused_imports)]` on by default
[INFO] [stderr] 
[INFO] [stderr] error: aborting due to 3 previous errors
[INFO] [stderr] 
[INFO] [stderr] Some errors have detailed explanations: E0423, E0425, E0433.
[INFO] [stderr] For more information about an error, try `rustc --explain E0423`.
[INFO] [stderr] error: Could not compile `libgitbox`.
[INFO] [stderr] 
[INFO] [stderr] To learn more, run the command again with --verbose.
[INFO] running `"docker" "inspect" "173e8f03a162c9e9b51be293b66311d17f9ddad3c7fd3f4aecf9b0ba964fd04e"`
[INFO] running `"docker" "rm" "-f" "173e8f03a162c9e9b51be293b66311d17f9ddad3c7fd3f4aecf9b0ba964fd04e"`
[INFO] [stdout] 173e8f03a162c9e9b51be293b66311d17f9ddad3c7fd3f4aecf9b0ba964fd04e