[INFO] crate burning-sanders 0.1.0 is already in cache
[INFO] checking burning-sanders-0.1.0 against master#7c59a81a5fcbaaca311f744cd7c68d99bfbb05d3 for pr-71873
[INFO] extracting crate burning-sanders 0.1.0 into /workspace/builds/worker-13/source
[INFO] validating manifest of crates.io crate burning-sanders 0.1.0 on toolchain 7c59a81a5fcbaaca311f744cd7c68d99bfbb05d3
[INFO] running `"/workspace/cargo-home/bin/cargo" "+7c59a81a5fcbaaca311f744cd7c68d99bfbb05d3" "read-manifest" "--manifest-path" "Cargo.toml"`
[INFO] started tweaking crates.io crate burning-sanders 0.1.0
[INFO] finished tweaking crates.io crate burning-sanders 0.1.0
[INFO] tweaked toml for crates.io crate burning-sanders 0.1.0 written to /workspace/builds/worker-13/source/Cargo.toml
[INFO] running `"/workspace/cargo-home/bin/cargo" "+7c59a81a5fcbaaca311f744cd7c68d99bfbb05d3" "generate-lockfile" "--manifest-path" "Cargo.toml" "-Zno-index-update"`
[INFO] running `"/workspace/cargo-home/bin/cargo" "+7c59a81a5fcbaaca311f744cd7c68d99bfbb05d3" "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-13/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-13/source/src/main.rs` was erroneously implicitly accepted for binary `sdr`,
[INFO] [stderr] please set bin.path in Cargo.toml
[INFO] [stderr]     Blocking waiting for file lock on package cache
[INFO] running `"docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-13/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-13/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" "+7c59a81a5fcbaaca311f744cd7c68d99bfbb05d3" "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] 4b49940284d79c3b7a18477b9e72a1fe33866ee64fbd95e7d5ff5759bfffdf53
[INFO] running `"docker" "start" "-a" "4b49940284d79c3b7a18477b9e72a1fe33866ee64fbd95e7d5ff5759bfffdf53"`
[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 `sdr`,
[INFO] [stderr] please set bin.path in Cargo.toml
[INFO] [stderr]    Compiling pkg-config v0.3.17
[INFO] [stderr]    Compiling libc v0.2.70
[INFO] [stderr]    Compiling log v0.4.8
[INFO] [stderr]    Compiling cc v1.0.53
[INFO] [stderr]     Checking cfg-if v0.1.10
[INFO] [stderr]     Checking log v0.3.9
[INFO] [stderr]    Compiling ncurses v5.99.0
[INFO] [stderr]     Checking pancurses v0.8.0
[INFO] [stderr]     Checking burning-sanders v0.1.0 (/opt/rustwide/workdir)
[INFO] [stderr] warning: this method call currently resolves to `<&[T; N] as IntoIterator>::into_iter` (due to autoref coercions), but that might change in the future when `IntoIterator` impls for arrays are added.
[INFO] [stderr]   --> src/main.rs:59:33
[INFO] [stderr]    |
[INFO] [stderr] 59 |   for (i, color) in COLOR_TABLE.into_iter().enumerate() {
[INFO] [stderr]    |                                 ^^^^^^^^^ help: use `.iter()` instead of `.into_iter()` to avoid ambiguity: `iter`
[INFO] [stderr]    |
[INFO] [stderr]    = note: `#[warn(array_into_iter)]` on by default
[INFO] [stderr]    = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in a future release!
[INFO] [stderr]    = note: for more information, see issue #66145 <https://github.com/rust-lang/rust/issues/66145>
[INFO] [stderr] 
[INFO] [stderr] warning: this method call currently resolves to `<&[T; N] as IntoIterator>::into_iter` (due to autoref coercions), but that might change in the future when `IntoIterator` impls for arrays are added.
[INFO] [stderr]   --> src/main.rs:59:33
[INFO] [stderr]    |
[INFO] [stderr] 59 |   for (i, color) in COLOR_TABLE.into_iter().enumerate() {
[INFO] [stderr]    |                                 ^^^^^^^^^ help: use `.iter()` instead of `.into_iter()` to avoid ambiguity: `iter`
[INFO] [stderr]    |
[INFO] [stderr]    = note: `#[warn(array_into_iter)]` on by default
[INFO] [stderr]    = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in a future release!
[INFO] [stderr]    = note: for more information, see issue #66145 <https://github.com/rust-lang/rust/issues/66145>
[INFO] [stderr] 
[INFO] [stderr] warning: 1 warning emitted
[INFO] [stderr] 
[INFO] [stderr] warning: 1 warning emitted
[INFO] [stderr] 
[INFO] [stderr]     Finished dev [unoptimized + debuginfo] target(s) in 9.19s
[INFO] running `"docker" "inspect" "4b49940284d79c3b7a18477b9e72a1fe33866ee64fbd95e7d5ff5759bfffdf53"`
[INFO] running `"docker" "rm" "-f" "4b49940284d79c3b7a18477b9e72a1fe33866ee64fbd95e7d5ff5759bfffdf53"`
[INFO] [stdout] 4b49940284d79c3b7a18477b9e72a1fe33866ee64fbd95e7d5ff5759bfffdf53