[INFO] crate pico-sys 0.0.1 is already in cache
[INFO] extracting crate pico-sys 0.0.1 into work/ex/pr-60039-1/sources/master#e305df1846a6d985315917ae0c81b74af8b4e641/reg/pico-sys/0.0.1
[INFO] extracting crate pico-sys 0.0.1 into work/ex/pr-60039-1/sources/try#99a7498759a22b5684caf798a98b7e90ad9d2443/reg/pico-sys/0.0.1
[INFO] validating manifest of pico-sys-0.0.1 on toolchain master#e305df1846a6d985315917ae0c81b74af8b4e641
[INFO] running `"/mnt/big/crater/work/local/cargo-home/bin/cargo" "+e305df1846a6d985315917ae0c81b74af8b4e641-alt" "read-manifest" "--manifest-path" "Cargo.toml"`
[INFO] validating manifest of pico-sys-0.0.1 on toolchain try#99a7498759a22b5684caf798a98b7e90ad9d2443
[INFO] running `"/mnt/big/crater/work/local/cargo-home/bin/cargo" "+99a7498759a22b5684caf798a98b7e90ad9d2443-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-60039-1/sources/master#e305df1846a6d985315917ae0c81b74af8b4e641/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-60039-1/sources/try#99a7498759a22b5684caf798a98b7e90ad9d2443/reg/pico-sys/0.0.1/Cargo.toml
[INFO] running `"/mnt/big/crater/work/local/cargo-home/bin/cargo" "+e305df1846a6d985315917ae0c81b74af8b4e641-alt" "generate-lockfile" "--manifest-path" "Cargo.toml" "-Zno-index-update"`
[INFO] running `"/mnt/big/crater/work/local/cargo-home/bin/cargo" "+99a7498759a22b5684caf798a98b7e90ad9d2443-alt" "generate-lockfile" "--manifest-path" "Cargo.toml" "-Zno-index-update"`
[INFO] running `"/mnt/big/crater/work/local/cargo-home/bin/cargo" "+e305df1846a6d985315917ae0c81b74af8b4e641-alt" "fetch" "--locked" "--manifest-path" "Cargo.toml"`
[INFO] running `"/mnt/big/crater/work/local/cargo-home/bin/cargo" "+99a7498759a22b5684caf798a98b7e90ad9d2443-alt" "fetch" "--locked" "--manifest-path" "Cargo.toml"`
[INFO] checking pico-sys-0.0.1 against try#99a7498759a22b5684caf798a98b7e90ad9d2443 for pr-60039-1
[INFO] running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/pr-60039-1/worker-4/try#99a7498759a22b5684caf798a98b7e90ad9d2443:/opt/crater/target:rw,Z" "-v" "/mnt/big/crater/work/ex/pr-60039-1/sources/try#99a7498759a22b5684caf798a98b7e90ad9d2443/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" "+99a7498759a22b5684caf798a98b7e90ad9d2443-alt" "check" "--frozen" "--all" "--all-targets"`
[INFO] [stdout] 271e2d244d9e2250cc6370efd2afe1aa4fc3a98aef9a7a9f4d092a7452705501
[INFO] running `"docker" "start" "-a" "271e2d244d9e2250cc6370efd2afe1aa4fc3a98aef9a7a9f4d092a7452705501"`
[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" "271e2d244d9e2250cc6370efd2afe1aa4fc3a98aef9a7a9f4d092a7452705501"`
[INFO] running `"docker" "rm" "-f" "271e2d244d9e2250cc6370efd2afe1aa4fc3a98aef9a7a9f4d092a7452705501"`
[INFO] [stdout] 271e2d244d9e2250cc6370efd2afe1aa4fc3a98aef9a7a9f4d092a7452705501