[INFO] crate bitrange 0.2.0 is already in cache
[INFO] checking bitrange-0.2.0 against master#45d050cde277b22a755847338f2acc2c7b834141 for pr-71393
[INFO] extracting crate bitrange 0.2.0 into /workspace/builds/worker-0/source
[INFO] validating manifest of crates.io crate bitrange 0.2.0 on toolchain 45d050cde277b22a755847338f2acc2c7b834141
[INFO] running `"/workspace/cargo-home/bin/cargo" "+45d050cde277b22a755847338f2acc2c7b834141" "read-manifest" "--manifest-path" "Cargo.toml"`
[INFO] started tweaking crates.io crate bitrange 0.2.0
[INFO] finished tweaking crates.io crate bitrange 0.2.0
[INFO] tweaked toml for crates.io crate bitrange 0.2.0 written to /workspace/builds/worker-0/source/Cargo.toml
[INFO] running `"/workspace/cargo-home/bin/cargo" "+45d050cde277b22a755847338f2acc2c7b834141" "generate-lockfile" "--manifest-path" "Cargo.toml" "-Zno-index-update"`
[INFO] running `"/workspace/cargo-home/bin/cargo" "+45d050cde277b22a755847338f2acc2c7b834141" "fetch" "--locked" "--manifest-path" "Cargo.toml"`
[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] * /workspace/builds/worker-0/source/src/bin/test_panics.rs
[INFO] [stderr] * /workspace/builds/worker-0/source/src/bin/test_ip.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] running `"docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-0/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-0/source:/opt/rustwide/workdir:ro,Z" "-v" "/var/lib/crater-agent-workspace/cargo-home:/opt/rustwide/cargo-home:ro,Z" "-v" "/var/lib/crater-agent-workspace/rustup-home:/opt/rustwide/rustup-home:ro,Z" "-e" "SOURCE_DIR=/opt/rustwide/workdir" "-e" "MAP_USER_ID=0" "-e" "CARGO_TARGET_DIR=/opt/rustwide/target" "-e" "CARGO_INCREMENTAL=0" "-e" "RUST_BACKTRACE=full" "-e" "RUSTFLAGS=--cap-lints=forbid" "-e" "CARGO_HOME=/opt/rustwide/cargo-home" "-e" "RUSTUP_HOME=/opt/rustwide/rustup-home" "-w" "/opt/rustwide/workdir" "-m" "1610612736" "--network" "none" "rustops/crates-build-env" "/opt/rustwide/cargo-home/bin/cargo" "+45d050cde277b22a755847338f2acc2c7b834141" "check" "--frozen" "--all" "--all-targets"`
[INFO] [stderr] WARNING: Your kernel does not support swap limit capabilities or the cgroup is not mounted. Memory limited without swap.
[INFO] [stdout] 206e6893fe629c40c053d2aeb74e30bda3152b9c9cecf197f359dfa3dbcf7017
[INFO] running `"docker" "start" "-a" "206e6893fe629c40c053d2aeb74e30bda3152b9c9cecf197f359dfa3dbcf7017"`
[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/rustwide/workdir/src/bin/test_panics.rs
[INFO] [stderr] * /opt/rustwide/workdir/src/bin/test_ip.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 bitrange_plugin v0.1.2
[INFO] [stderr] error[E0599]: no variant or associated item named `Term` found for enum `proc_macro::TokenTree` in the current scope
[INFO] [stderr]   --> /opt/rustwide/cargo-home/registry/src/github.com-1ecc6299db9ec823/bitrange_plugin-0.1.2/src/pattern.rs:60:37
[INFO] [stderr]    |
[INFO] [stderr] 60 |                     Some(TokenTree::Term(term)) => {
[INFO] [stderr]    |                                     ^^^^ variant or associated item not found in `proc_macro::TokenTree`
[INFO] [stderr] 
[INFO] [stderr] error[E0599]: no variant or associated item named `Op` found for enum `proc_macro::TokenTree` in the current scope
[INFO] [stderr]   --> /opt/rustwide/cargo-home/registry/src/github.com-1ecc6299db9ec823/bitrange_plugin-0.1.2/src/pattern.rs:85:28
[INFO] [stderr]    |
[INFO] [stderr] 85 |     if let Some(TokenTree::Op(op)) = item {
[INFO] [stderr]    |                            ^^ variant or associated item not found in `proc_macro::TokenTree`
[INFO] [stderr] 
[INFO] [stderr] error[E0599]: no variant or associated item named `Term` found for enum `proc_macro::TokenTree` in the current scope
[INFO] [stderr]   --> /opt/rustwide/cargo-home/registry/src/github.com-1ecc6299db9ec823/bitrange_plugin-0.1.2/src/pattern.rs:97:28
[INFO] [stderr]    |
[INFO] [stderr] 97 |     if let Some(TokenTree::Term(term)) = item {
[INFO] [stderr]    |                            ^^^^ variant or associated item not found in `proc_macro::TokenTree`
[INFO] [stderr] 
[INFO] [stderr] error: aborting due to 3 previous errors
[INFO] [stderr] 
[INFO] [stderr] For more information about this error, try `rustc --explain E0599`.
[INFO] [stderr] error: could not compile `bitrange_plugin`.
[INFO] [stderr] 
[INFO] [stderr] To learn more, run the command again with --verbose.
[INFO] running `"docker" "inspect" "206e6893fe629c40c053d2aeb74e30bda3152b9c9cecf197f359dfa3dbcf7017"`
[INFO] running `"docker" "rm" "-f" "206e6893fe629c40c053d2aeb74e30bda3152b9c9cecf197f359dfa3dbcf7017"`
[INFO] [stdout] 206e6893fe629c40c053d2aeb74e30bda3152b9c9cecf197f359dfa3dbcf7017