[INFO] fetching crate mml 0.1.41... [INFO] testing mml-0.1.41 against beta-2020-06-03 for beta-1.45-1 [INFO] extracting crate mml 0.1.41 into /workspace/builds/worker-1/source [INFO] validating manifest of crates.io crate mml 0.1.41 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 mml 0.1.41 [INFO] finished tweaking crates.io crate mml 0.1.41 [INFO] tweaked toml for crates.io crate mml 0.1.41 written to /workspace/builds/worker-1/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-1/source/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 `/workspace/builds/worker-1/source/src/main.rs` was erroneously implicitly accepted for binary `ml`, [INFO] [stderr] please set bin.path in Cargo.toml [INFO] running `"docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-1/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-1/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] [stderr] WARNING: Your kernel does not support swap limit capabilities or the cgroup is not mounted. Memory limited without swap. [INFO] [stdout] c2c97981a0590437eadcc04c8dac57497f31501a76c234485b592e9756870985 [INFO] running `"docker" "start" "-a" "c2c97981a0590437eadcc04c8dac57497f31501a76c234485b592e9756870985"` [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/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/rustwide/workdir/src/main.rs` was erroneously implicitly accepted for binary `ml`, [INFO] [stderr] please set bin.path in Cargo.toml [INFO] [stderr] Compiling same-file v0.1.3 [INFO] [stderr] Compiling dot v0.1.4 [INFO] [stderr] Compiling itertools v0.5.10 [INFO] [stderr] Compiling syntex_errors v0.58.1 [INFO] [stderr] Compiling walkdir v1.0.7 [INFO] [stderr] Compiling syntex_syntax v0.58.1 [INFO] [stderr] error[E0423]: expected function, tuple struct or tuple variant, found struct `ast::Name` [INFO] [stderr] --> /opt/rustwide/cargo-home/registry/src/github.com-1ecc6299db9ec823/syntex_syntax-0.58.1/src/symbol.rs:146:27 [INFO] [stderr] | [INFO] [stderr] 146 | name: ast::Name($index), [INFO] [stderr] | ^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 165 | / declare_keywords! { [INFO] [stderr] 166 | | // Invalid identifier [INFO] [stderr] 167 | | (0, Invalid, "") [INFO] [stderr] 168 | | [INFO] [stderr] ... | [INFO] [stderr] 231 | | (56, CrateRoot, "{{root}}") [INFO] [stderr] 232 | | } [INFO] [stderr] | |_- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] error: aborting due to previous error [INFO] [stderr] [INFO] [stderr] For more information about this error, try `rustc --explain E0423`. [INFO] [stderr] error: could not compile `syntex_syntax`. [INFO] [stderr] [INFO] [stderr] To learn more, run the command again with --verbose. [INFO] running `"docker" "inspect" "c2c97981a0590437eadcc04c8dac57497f31501a76c234485b592e9756870985"` [INFO] running `"docker" "rm" "-f" "c2c97981a0590437eadcc04c8dac57497f31501a76c234485b592e9756870985"` [INFO] [stdout] c2c97981a0590437eadcc04c8dac57497f31501a76c234485b592e9756870985