[INFO] crate byte_trie 0.3.0 is already in cache [INFO] extracting crate byte_trie 0.3.0 into work/ex/pr-63376/sources/master#60960a260f7b5c695fd0717311d72ce62dd4eb43/reg/byte_trie/0.3.0 [INFO] extracting crate byte_trie 0.3.0 into work/ex/pr-63376/sources/try#266783e4e09e4e9d5307c1c8e695659c58bbcac7/reg/byte_trie/0.3.0 [INFO] validating manifest of byte_trie-0.3.0 on toolchain master#60960a260f7b5c695fd0717311d72ce62dd4eb43 [INFO] running `"/mnt/big/crater/work/local/cargo-home/bin/cargo" "+60960a260f7b5c695fd0717311d72ce62dd4eb43-alt" "read-manifest" "--manifest-path" "Cargo.toml"` [INFO] validating manifest of byte_trie-0.3.0 on toolchain try#266783e4e09e4e9d5307c1c8e695659c58bbcac7 [INFO] running `"/mnt/big/crater/work/local/cargo-home/bin/cargo" "+266783e4e09e4e9d5307c1c8e695659c58bbcac7-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-63376/sources/master#60960a260f7b5c695fd0717311d72ce62dd4eb43/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-63376/sources/try#266783e4e09e4e9d5307c1c8e695659c58bbcac7/reg/byte_trie/0.3.0/Cargo.toml [INFO] running `"/mnt/big/crater/work/local/cargo-home/bin/cargo" "+60960a260f7b5c695fd0717311d72ce62dd4eb43-alt" "generate-lockfile" "--manifest-path" "Cargo.toml" "-Zno-index-update"` [INFO] running `"/mnt/big/crater/work/local/cargo-home/bin/cargo" "+266783e4e09e4e9d5307c1c8e695659c58bbcac7-alt" "generate-lockfile" "--manifest-path" "Cargo.toml" "-Zno-index-update"` [INFO] running `"/mnt/big/crater/work/local/cargo-home/bin/cargo" "+60960a260f7b5c695fd0717311d72ce62dd4eb43-alt" "fetch" "--locked" "--manifest-path" "Cargo.toml"` [INFO] running `"/mnt/big/crater/work/local/cargo-home/bin/cargo" "+266783e4e09e4e9d5307c1c8e695659c58bbcac7-alt" "fetch" "--locked" "--manifest-path" "Cargo.toml"` [INFO] checking byte_trie-0.3.0 against master#60960a260f7b5c695fd0717311d72ce62dd4eb43 for pr-63376 [INFO] running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/pr-63376/worker-5/master#60960a260f7b5c695fd0717311d72ce62dd4eb43:/opt/crater/target:rw,Z" "-v" "/mnt/big/crater/work/ex/pr-63376/sources/master#60960a260f7b5c695fd0717311d72ce62dd4eb43/reg/byte_trie/0.3.0:/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" "+60960a260f7b5c695fd0717311d72ce62dd4eb43-alt" "check" "--frozen" "--all" "--all-targets"` [INFO] [stdout] 1246aa25e39dea6fc76929da4da798cd5083f19e97a39f0de018a4f1ac10b11d [INFO] running `"docker" "start" "-a" "1246aa25e39dea6fc76929da4da798cd5083f19e97a39f0de018a4f1ac10b11d"` [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" "1246aa25e39dea6fc76929da4da798cd5083f19e97a39f0de018a4f1ac10b11d"` [INFO] running `"docker" "rm" "-f" "1246aa25e39dea6fc76929da4da798cd5083f19e97a39f0de018a4f1ac10b11d"` [INFO] [stdout] 1246aa25e39dea6fc76929da4da798cd5083f19e97a39f0de018a4f1ac10b11d