[INFO] crate pylon-sys 0.1.1 is already in cache [INFO] extracting crate pylon-sys 0.1.1 into work/ex/pr-60932/sources/master#548add7f61bfcbe3bea3f5ccefb53c84da8fefe4/reg/pylon-sys/0.1.1 [INFO] extracting crate pylon-sys 0.1.1 into work/ex/pr-60932/sources/try#097e26225c5cc28d3042ad4c80eac7c488f78ee7/reg/pylon-sys/0.1.1 [INFO] validating manifest of pylon-sys-0.1.1 on toolchain master#548add7f61bfcbe3bea3f5ccefb53c84da8fefe4 [INFO] running `"/mnt/crater-raid/crater/work/local/cargo-home/bin/cargo" "+548add7f61bfcbe3bea3f5ccefb53c84da8fefe4-alt" "read-manifest" "--manifest-path" "Cargo.toml"` [INFO] validating manifest of pylon-sys-0.1.1 on toolchain try#097e26225c5cc28d3042ad4c80eac7c488f78ee7 [INFO] running `"/mnt/crater-raid/crater/work/local/cargo-home/bin/cargo" "+097e26225c5cc28d3042ad4c80eac7c488f78ee7-alt" "read-manifest" "--manifest-path" "Cargo.toml"` [INFO] started frobbing pylon-sys-0.1.1 [INFO] finished frobbing pylon-sys-0.1.1 [INFO] frobbed toml for pylon-sys-0.1.1 written to work/ex/pr-60932/sources/master#548add7f61bfcbe3bea3f5ccefb53c84da8fefe4/reg/pylon-sys/0.1.1/Cargo.toml [INFO] started frobbing pylon-sys-0.1.1 [INFO] finished frobbing pylon-sys-0.1.1 [INFO] frobbed toml for pylon-sys-0.1.1 written to work/ex/pr-60932/sources/try#097e26225c5cc28d3042ad4c80eac7c488f78ee7/reg/pylon-sys/0.1.1/Cargo.toml [INFO] running `"/mnt/crater-raid/crater/work/local/cargo-home/bin/cargo" "+548add7f61bfcbe3bea3f5ccefb53c84da8fefe4-alt" "generate-lockfile" "--manifest-path" "Cargo.toml" "-Zno-index-update"` [INFO] running `"/mnt/crater-raid/crater/work/local/cargo-home/bin/cargo" "+097e26225c5cc28d3042ad4c80eac7c488f78ee7-alt" "generate-lockfile" "--manifest-path" "Cargo.toml" "-Zno-index-update"` [INFO] running `"/mnt/crater-raid/crater/work/local/cargo-home/bin/cargo" "+548add7f61bfcbe3bea3f5ccefb53c84da8fefe4-alt" "fetch" "--locked" "--manifest-path" "Cargo.toml"` [INFO] running `"/mnt/crater-raid/crater/work/local/cargo-home/bin/cargo" "+097e26225c5cc28d3042ad4c80eac7c488f78ee7-alt" "fetch" "--locked" "--manifest-path" "Cargo.toml"` [INFO] checking pylon-sys-0.1.1 against master#548add7f61bfcbe3bea3f5ccefb53c84da8fefe4 for pr-60932 [INFO] running `"docker" "create" "-v" "/mnt/crater-raid/crater/work/local/target-dirs/pr-60932/worker-6/master#548add7f61bfcbe3bea3f5ccefb53c84da8fefe4:/opt/crater/target:rw,Z" "-v" "/mnt/crater-raid/crater/work/ex/pr-60932/sources/master#548add7f61bfcbe3bea3f5ccefb53c84da8fefe4/reg/pylon-sys/0.1.1:/opt/crater/workdir:ro,Z" "-v" "/mnt/crater-raid/crater/work/local/cargo-home:/opt/crater/cargo-home:ro,Z" "-v" "/mnt/crater-raid/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" "+548add7f61bfcbe3bea3f5ccefb53c84da8fefe4-alt" "check" "--frozen" "--all" "--all-targets"` [INFO] [stdout] ccec1bf79449412d8a68443d5ed47540f0e6b22d68776813e2956e8255376e31 [INFO] running `"docker" "start" "-a" "ccec1bf79449412d8a68443d5ed47540f0e6b22d68776813e2956e8255376e31"` [INFO] [stderr] Compiling pylon-sys v0.1.1 (/opt/crater/workdir) [INFO] [stderr] error: environment variable `PYLON_ROOT` not defined [INFO] [stderr] --> build.rs:7:22 [INFO] [stderr] | [INFO] [stderr] 7 | let pylon_root = env!("PYLON_ROOT"); [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^ [INFO] [stderr] [INFO] [stderr] warning: unused import: `Path` [INFO] [stderr] --> build.rs:3:17 [INFO] [stderr] | [INFO] [stderr] 3 | use std::path::{Path, PathBuf}; [INFO] [stderr] | ^^^^ [INFO] [stderr] | [INFO] [stderr] = note: #[warn(unused_imports)] on by default [INFO] [stderr] [INFO] [stderr] error: aborting due to previous error [INFO] [stderr] [INFO] [stderr] error: Could not compile `pylon-sys`. [INFO] [stderr] [INFO] [stderr] To learn more, run the command again with --verbose. [INFO] running `"docker" "inspect" "ccec1bf79449412d8a68443d5ed47540f0e6b22d68776813e2956e8255376e31"` [INFO] running `"docker" "rm" "-f" "ccec1bf79449412d8a68443d5ed47540f0e6b22d68776813e2956e8255376e31"` [INFO] [stdout] ccec1bf79449412d8a68443d5ed47540f0e6b22d68776813e2956e8255376e31