[INFO] crate pico-sys 0.0.1 is already in cache [INFO] extracting crate pico-sys 0.0.1 into work/ex/pr-58948/sources/master#0f88167f89fffe321590c5148f21b7d51d44388d/reg/pico-sys/0.0.1 [INFO] extracting crate pico-sys 0.0.1 into work/ex/pr-58948/sources/try#a829e31f924ec11e400e8d0c2fd2c4bb8937ae6b/reg/pico-sys/0.0.1 [INFO] validating manifest of pico-sys-0.0.1 on toolchain master#0f88167f89fffe321590c5148f21b7d51d44388d [INFO] running `"/mnt/big/crater/work/local/cargo-home/bin/cargo" "+0f88167f89fffe321590c5148f21b7d51d44388d-alt" "read-manifest" "--manifest-path" "Cargo.toml"` [INFO] validating manifest of pico-sys-0.0.1 on toolchain try#a829e31f924ec11e400e8d0c2fd2c4bb8937ae6b [INFO] running `"/mnt/big/crater/work/local/cargo-home/bin/cargo" "+a829e31f924ec11e400e8d0c2fd2c4bb8937ae6b-alt" "read-manifest" "--manifest-path" "Cargo.toml"` [INFO] started frobbing pico-sys-0.0.1 [INFO] finished frobbing pico-sys-0.0.1 [INFO] frobbed toml for pico-sys-0.0.1 written to work/ex/pr-58948/sources/master#0f88167f89fffe321590c5148f21b7d51d44388d/reg/pico-sys/0.0.1/Cargo.toml [INFO] started frobbing pico-sys-0.0.1 [INFO] finished frobbing pico-sys-0.0.1 [INFO] frobbed toml for pico-sys-0.0.1 written to work/ex/pr-58948/sources/try#a829e31f924ec11e400e8d0c2fd2c4bb8937ae6b/reg/pico-sys/0.0.1/Cargo.toml [INFO] running `"/mnt/big/crater/work/local/cargo-home/bin/cargo" "+0f88167f89fffe321590c5148f21b7d51d44388d-alt" "generate-lockfile" "--manifest-path" "Cargo.toml" "-Zno-index-update"` [INFO] running `"/mnt/big/crater/work/local/cargo-home/bin/cargo" "+a829e31f924ec11e400e8d0c2fd2c4bb8937ae6b-alt" "generate-lockfile" "--manifest-path" "Cargo.toml" "-Zno-index-update"` [INFO] running `"/mnt/big/crater/work/local/cargo-home/bin/cargo" "+0f88167f89fffe321590c5148f21b7d51d44388d-alt" "fetch" "--locked" "--manifest-path" "Cargo.toml"` [INFO] running `"/mnt/big/crater/work/local/cargo-home/bin/cargo" "+a829e31f924ec11e400e8d0c2fd2c4bb8937ae6b-alt" "fetch" "--locked" "--manifest-path" "Cargo.toml"` [INFO] checking pico-sys-0.0.1 against try#a829e31f924ec11e400e8d0c2fd2c4bb8937ae6b for pr-58948 [INFO] running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/pr-58948/worker-4/try#a829e31f924ec11e400e8d0c2fd2c4bb8937ae6b:/opt/crater/target:rw,Z" "-v" "/mnt/big/crater/work/ex/pr-58948/sources/try#a829e31f924ec11e400e8d0c2fd2c4bb8937ae6b/reg/pico-sys/0.0.1:/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" "+a829e31f924ec11e400e8d0c2fd2c4bb8937ae6b-alt" "check" "--frozen" "--all" "--all-targets"` [INFO] [stdout] 782bcf9c3079fb825442112c7cad788a501756c3ff6614357949cf1b69f3d0c6 [INFO] running `"docker" "start" "-a" "782bcf9c3079fb825442112c7cad788a501756c3ff6614357949cf1b69f3d0c6"` [INFO] [stderr] Compiling pico-sys v0.0.1 (/opt/crater/workdir) [INFO] [stderr] error: use of deprecated item 'gcc::compile_library': crate has been renamed to `cc`, the `gcc` name is not maintained [INFO] [stderr] --> build.rs:6:5 [INFO] [stderr] | [INFO] [stderr] 6 | gcc::compile_library( [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] note: lint level defined here [INFO] [stderr] --> build.rs:1:9 [INFO] [stderr] | [INFO] [stderr] 1 | #![deny(warnings)] [INFO] [stderr] | ^^^^^^^^ [INFO] [stderr] = note: #[deny(deprecated)] implied by #[deny(warnings)] [INFO] [stderr] [INFO] [stderr] error: aborting due to previous error [INFO] [stderr] [INFO] [stderr] error: Could not compile `pico-sys`. [INFO] [stderr] [INFO] [stderr] To learn more, run the command again with --verbose. [INFO] running `"docker" "inspect" "782bcf9c3079fb825442112c7cad788a501756c3ff6614357949cf1b69f3d0c6"` [INFO] running `"docker" "rm" "-f" "782bcf9c3079fb825442112c7cad788a501756c3ff6614357949cf1b69f3d0c6"` [INFO] [stdout] 782bcf9c3079fb825442112c7cad788a501756c3ff6614357949cf1b69f3d0c6