[INFO] crate bitrange 0.2.0 is already in cache [INFO] testing bitrange-0.2.0 against beta-2020-06-03 for beta-1.45-1 [INFO] extracting crate bitrange 0.2.0 into /workspace/builds/worker-5/source [INFO] validating manifest of crates.io crate bitrange 0.2.0 on toolchain beta-2020-06-03 [INFO] running `"/workspace/cargo-home/bin/cargo" "+beta-2020-06-03" "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-5/source/Cargo.toml [INFO] running `"/workspace/cargo-home/bin/cargo" "+beta-2020-06-03" "generate-lockfile" "--manifest-path" "Cargo.toml" "-Zno-index-update"` [INFO] running `"/workspace/cargo-home/bin/cargo" "+beta-2020-06-03" "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-5/source/src/bin/test_ip.rs [INFO] [stderr] * /workspace/builds/worker-5/source/src/bin/test_panics.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-5/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-5/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=warn" "-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" "+beta-2020-06-03" "build" "--frozen"` [INFO] [stdout] 129c84fe8ef4c1f68f10da5237f4c23576f5fd334dc77bfa388c7199b32d79ba [INFO] [stderr] WARNING: Your kernel does not support swap limit capabilities or the cgroup is not mounted. Memory limited without swap. [INFO] running `"docker" "start" "-a" "129c84fe8ef4c1f68f10da5237f4c23576f5fd334dc77bfa388c7199b32d79ba"` [INFO] [stderr] sudo: setrlimit(RLIMIT_CORE): Operation not permitted [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_ip.rs [INFO] [stderr] * /opt/rustwide/workdir/src/bin/test_panics.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[E0554]: `#![feature]` may not be used on the beta release channel [INFO] [stderr] --> /opt/rustwide/cargo-home/registry/src/github.com-1ecc6299db9ec823/bitrange_plugin-0.1.2/src/lib.rs:2:1 [INFO] [stderr] | [INFO] [stderr] 2 | #![feature(proc_macro)] [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^ [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: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 4 previous errors [INFO] [stderr] [INFO] [stderr] Some errors have detailed explanations: E0554, E0599. [INFO] [stderr] For more information about an error, try `rustc --explain E0554`. [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" "129c84fe8ef4c1f68f10da5237f4c23576f5fd334dc77bfa388c7199b32d79ba"` [INFO] running `"docker" "rm" "-f" "129c84fe8ef4c1f68f10da5237f4c23576f5fd334dc77bfa388c7199b32d79ba"` [INFO] [stdout] 129c84fe8ef4c1f68f10da5237f4c23576f5fd334dc77bfa388c7199b32d79ba