[INFO] crate processortrace 0.0.1 is already in cache
[INFO] extracting crate processortrace 0.0.1 into work/ex/pr-59527/sources/master#003382e4150984cb476047b3925edf8d75df2d59/reg/processortrace/0.0.1
[INFO] extracting crate processortrace 0.0.1 into work/ex/pr-59527/sources/try#47f4f94676fbdd494dd2c2dc9ac377a13fc78e00/reg/processortrace/0.0.1
[INFO] validating manifest of processortrace-0.0.1 on toolchain master#003382e4150984cb476047b3925edf8d75df2d59
[INFO] running `"/mnt/crater-raid/crater/work/local/cargo-home/bin/cargo" "+003382e4150984cb476047b3925edf8d75df2d59-alt" "read-manifest" "--manifest-path" "Cargo.toml"`
[INFO] validating manifest of processortrace-0.0.1 on toolchain try#47f4f94676fbdd494dd2c2dc9ac377a13fc78e00
[INFO] running `"/mnt/crater-raid/crater/work/local/cargo-home/bin/cargo" "+47f4f94676fbdd494dd2c2dc9ac377a13fc78e00-alt" "read-manifest" "--manifest-path" "Cargo.toml"`
[INFO] started frobbing processortrace-0.0.1
[INFO] finished frobbing processortrace-0.0.1
[INFO] frobbed toml for processortrace-0.0.1 written to work/ex/pr-59527/sources/master#003382e4150984cb476047b3925edf8d75df2d59/reg/processortrace/0.0.1/Cargo.toml
[INFO] started frobbing processortrace-0.0.1
[INFO] finished frobbing processortrace-0.0.1
[INFO] frobbed toml for processortrace-0.0.1 written to work/ex/pr-59527/sources/try#47f4f94676fbdd494dd2c2dc9ac377a13fc78e00/reg/processortrace/0.0.1/Cargo.toml
[INFO] running `"/mnt/crater-raid/crater/work/local/cargo-home/bin/cargo" "+003382e4150984cb476047b3925edf8d75df2d59-alt" "generate-lockfile" "--manifest-path" "Cargo.toml" "-Zno-index-update"`
[INFO] running `"/mnt/crater-raid/crater/work/local/cargo-home/bin/cargo" "+47f4f94676fbdd494dd2c2dc9ac377a13fc78e00-alt" "generate-lockfile" "--manifest-path" "Cargo.toml" "-Zno-index-update"`
[INFO] running `"/mnt/crater-raid/crater/work/local/cargo-home/bin/cargo" "+003382e4150984cb476047b3925edf8d75df2d59-alt" "fetch" "--locked" "--manifest-path" "Cargo.toml"`
[INFO] running `"/mnt/crater-raid/crater/work/local/cargo-home/bin/cargo" "+47f4f94676fbdd494dd2c2dc9ac377a13fc78e00-alt" "fetch" "--locked" "--manifest-path" "Cargo.toml"`
[INFO] checking processortrace-0.0.1 against try#47f4f94676fbdd494dd2c2dc9ac377a13fc78e00 for pr-59527
[INFO] running `"docker" "create" "-v" "/mnt/crater-raid/crater/work/local/target-dirs/pr-59527/worker-5/try#47f4f94676fbdd494dd2c2dc9ac377a13fc78e00:/opt/crater/target:rw,Z" "-v" "/mnt/crater-raid/crater/work/ex/pr-59527/sources/try#47f4f94676fbdd494dd2c2dc9ac377a13fc78e00/reg/processortrace/0.0.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" "+47f4f94676fbdd494dd2c2dc9ac377a13fc78e00-alt" "check" "--frozen" "--all" "--all-targets"`
[INFO] [stdout] 232f57d71a8956404180af00aef6b51c2fc8cc027004e31aaf1911efb03d46e4
[INFO] running `"docker" "start" "-a" "232f57d71a8956404180af00aef6b51c2fc8cc027004e31aaf1911efb03d46e4"`
[INFO] [stderr]    Compiling x86 v0.11.0
[INFO] [stderr]     Checking driverkit v0.2.0
[INFO] [stderr]     Checking processortrace v0.0.1 (/opt/crater/workdir)
[INFO] [stderr] error[E0463]: can't find crate for `nix`
[INFO] [stderr]   --> src/lib.rs:20:1
[INFO] [stderr]    |
[INFO] [stderr] 20 | extern crate nix;
[INFO] [stderr]    | ^^^^^^^^^^^^^^^^^ can't find crate
[INFO] [stderr] 
[INFO] [stderr] error: aborting due to previous error
[INFO] [stderr] 
[INFO] [stderr] For more information about this error, try `rustc --explain E0463`.
[INFO] [stderr] error: Could not compile `processortrace`.
[INFO] [stderr] 
[INFO] [stderr] To learn more, run the command again with --verbose.
[INFO] running `"docker" "inspect" "232f57d71a8956404180af00aef6b51c2fc8cc027004e31aaf1911efb03d46e4"`
[INFO] running `"docker" "rm" "-f" "232f57d71a8956404180af00aef6b51c2fc8cc027004e31aaf1911efb03d46e4"`
[INFO] [stdout] 232f57d71a8956404180af00aef6b51c2fc8cc027004e31aaf1911efb03d46e4