[INFO] crate byte_trie 0.3.0 is already in cache
[INFO] extracting crate byte_trie 0.3.0 into work/ex/pr-60914/sources/master#39401465da4ce27aeeb2c2a26133ac35c63aa515/reg/byte_trie/0.3.0
[INFO] extracting crate byte_trie 0.3.0 into work/ex/pr-60914/sources/try#f45cc3094ee337acd688771b9234318046b0572d/reg/byte_trie/0.3.0
[INFO] validating manifest of byte_trie-0.3.0 on toolchain master#39401465da4ce27aeeb2c2a26133ac35c63aa515
[INFO] running `"/mnt/crater-raid/crater/work/local/cargo-home/bin/cargo" "+39401465da4ce27aeeb2c2a26133ac35c63aa515-alt" "read-manifest" "--manifest-path" "Cargo.toml"`
[INFO] validating manifest of byte_trie-0.3.0 on toolchain try#f45cc3094ee337acd688771b9234318046b0572d
[INFO] running `"/mnt/crater-raid/crater/work/local/cargo-home/bin/cargo" "+f45cc3094ee337acd688771b9234318046b0572d-alt" "read-manifest" "--manifest-path" "Cargo.toml"`
[INFO] started frobbing byte_trie-0.3.0
[INFO] finished frobbing byte_trie-0.3.0
[INFO] frobbed toml for byte_trie-0.3.0 written to work/ex/pr-60914/sources/master#39401465da4ce27aeeb2c2a26133ac35c63aa515/reg/byte_trie/0.3.0/Cargo.toml
[INFO] started frobbing byte_trie-0.3.0
[INFO] finished frobbing byte_trie-0.3.0
[INFO] frobbed toml for byte_trie-0.3.0 written to work/ex/pr-60914/sources/try#f45cc3094ee337acd688771b9234318046b0572d/reg/byte_trie/0.3.0/Cargo.toml
[INFO] running `"/mnt/crater-raid/crater/work/local/cargo-home/bin/cargo" "+39401465da4ce27aeeb2c2a26133ac35c63aa515-alt" "generate-lockfile" "--manifest-path" "Cargo.toml" "-Zno-index-update"`
[INFO] running `"/mnt/crater-raid/crater/work/local/cargo-home/bin/cargo" "+f45cc3094ee337acd688771b9234318046b0572d-alt" "generate-lockfile" "--manifest-path" "Cargo.toml" "-Zno-index-update"`
[INFO] running `"/mnt/crater-raid/crater/work/local/cargo-home/bin/cargo" "+39401465da4ce27aeeb2c2a26133ac35c63aa515-alt" "fetch" "--locked" "--manifest-path" "Cargo.toml"`
[INFO] running `"/mnt/crater-raid/crater/work/local/cargo-home/bin/cargo" "+f45cc3094ee337acd688771b9234318046b0572d-alt" "fetch" "--locked" "--manifest-path" "Cargo.toml"`
[INFO] checking byte_trie-0.3.0 against try#f45cc3094ee337acd688771b9234318046b0572d for pr-60914
[INFO] running `"docker" "create" "-v" "/mnt/crater-raid/crater/work/local/target-dirs/pr-60914/worker-3/try#f45cc3094ee337acd688771b9234318046b0572d:/opt/crater/target:rw,Z" "-v" "/mnt/crater-raid/crater/work/ex/pr-60914/sources/try#f45cc3094ee337acd688771b9234318046b0572d/reg/byte_trie/0.3.0:/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" "+f45cc3094ee337acd688771b9234318046b0572d-alt" "check" "--frozen" "--all" "--all-targets"`
[INFO] [stdout] ae2fedfc68b5d34410ac9045216c272b1b145c6ea4d11483dd92b5670e3d3f10
[INFO] running `"docker" "start" "-a" "ae2fedfc68b5d34410ac9045216c272b1b145c6ea4d11483dd92b5670e3d3f10"`
[INFO] [stderr]     Checking byte_trie v0.3.0 (/opt/crater/workdir)
[INFO] [stderr] error[E0432]: unresolved import `byte_trie::ByteTrie`
[INFO] [stderr]  --> benches/inserting.rs:1:5
[INFO] [stderr]   |
[INFO] [stderr] 1 | use byte_trie::ByteTrie;
[INFO] [stderr]   |     ^^^^^^^^^^^--------
[INFO] [stderr]   |     |          |
[INFO] [stderr]   |     |          help: a similar name exists in the module: `BytesTrie`
[INFO] [stderr]   |     no `ByteTrie` in the root
[INFO] [stderr] 
[INFO] [stderr] error: aborting due to previous error
[INFO] [stderr] 
[INFO] [stderr] For more information about this error, try `rustc --explain E0432`.
[INFO] [stderr] error: Could not compile `byte_trie`.
[INFO] [stderr] 
[INFO] [stderr] To learn more, run the command again with --verbose.
[INFO] running `"docker" "inspect" "ae2fedfc68b5d34410ac9045216c272b1b145c6ea4d11483dd92b5670e3d3f10"`
[INFO] running `"docker" "rm" "-f" "ae2fedfc68b5d34410ac9045216c272b1b145c6ea4d11483dd92b5670e3d3f10"`
[INFO] [stdout] ae2fedfc68b5d34410ac9045216c272b1b145c6ea4d11483dd92b5670e3d3f10