[INFO] crate trie-db 0.12.2 is already in cache [INFO] extracting crate trie-db 0.12.2 into work/ex/pr-60039/sources/master#efe2f32a6b8217425f361ec7c206910c611c03ee/reg/trie-db/0.12.2 [INFO] extracting crate trie-db 0.12.2 into work/ex/pr-60039/sources/try#78b0bd8441ef961f6475e3d47fe3bca38cb83432/reg/trie-db/0.12.2 [INFO] validating manifest of trie-db-0.12.2 on toolchain master#efe2f32a6b8217425f361ec7c206910c611c03ee [INFO] running `"/mnt/big/crater/work/local/cargo-home/bin/cargo" "+efe2f32a6b8217425f361ec7c206910c611c03ee-alt" "read-manifest" "--manifest-path" "Cargo.toml"` [INFO] validating manifest of trie-db-0.12.2 on toolchain try#78b0bd8441ef961f6475e3d47fe3bca38cb83432 [INFO] running `"/mnt/big/crater/work/local/cargo-home/bin/cargo" "+78b0bd8441ef961f6475e3d47fe3bca38cb83432-alt" "read-manifest" "--manifest-path" "Cargo.toml"` [INFO] started frobbing trie-db-0.12.2 [INFO] finished frobbing trie-db-0.12.2 [INFO] frobbed toml for trie-db-0.12.2 written to work/ex/pr-60039/sources/master#efe2f32a6b8217425f361ec7c206910c611c03ee/reg/trie-db/0.12.2/Cargo.toml [INFO] started frobbing trie-db-0.12.2 [INFO] finished frobbing trie-db-0.12.2 [INFO] frobbed toml for trie-db-0.12.2 written to work/ex/pr-60039/sources/try#78b0bd8441ef961f6475e3d47fe3bca38cb83432/reg/trie-db/0.12.2/Cargo.toml [INFO] running `"/mnt/big/crater/work/local/cargo-home/bin/cargo" "+efe2f32a6b8217425f361ec7c206910c611c03ee-alt" "generate-lockfile" "--manifest-path" "Cargo.toml" "-Zno-index-update"` [INFO] running `"/mnt/big/crater/work/local/cargo-home/bin/cargo" "+78b0bd8441ef961f6475e3d47fe3bca38cb83432-alt" "generate-lockfile" "--manifest-path" "Cargo.toml" "-Zno-index-update"` [INFO] running `"/mnt/big/crater/work/local/cargo-home/bin/cargo" "+efe2f32a6b8217425f361ec7c206910c611c03ee-alt" "fetch" "--locked" "--manifest-path" "Cargo.toml"` [INFO] running `"/mnt/big/crater/work/local/cargo-home/bin/cargo" "+78b0bd8441ef961f6475e3d47fe3bca38cb83432-alt" "fetch" "--locked" "--manifest-path" "Cargo.toml"` [INFO] checking trie-db-0.12.2 against try#78b0bd8441ef961f6475e3d47fe3bca38cb83432 for pr-60039 [INFO] running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/pr-60039/worker-0/try#78b0bd8441ef961f6475e3d47fe3bca38cb83432:/opt/crater/target:rw,Z" "-v" "/mnt/big/crater/work/ex/pr-60039/sources/try#78b0bd8441ef961f6475e3d47fe3bca38cb83432/reg/trie-db/0.12.2:/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" "+78b0bd8441ef961f6475e3d47fe3bca38cb83432-alt" "check" "--frozen" "--all" "--all-targets"` [INFO] [stdout] f1fcd116f886fab7f4858d3f99172c7b6d749ed618f81b2a7a9cb8d9c4053bcc [INFO] running `"docker" "start" "-a" "f1fcd116f886fab7f4858d3f99172c7b6d749ed618f81b2a7a9cb8d9c4053bcc"` [INFO] [stderr] Checking hashmap_core v0.1.10 [INFO] [stderr] Checking trie-root v0.12.2 [INFO] [stderr] Checking elastic-array v0.10.2 [INFO] [stderr] Checking criterion v0.2.11 [INFO] [stderr] Checking env_logger v0.6.1 [INFO] [stderr] Checking memory-db v0.12.2 [INFO] [stderr] Checking trie-db v0.12.2 (/opt/crater/workdir) [INFO] [stderr] Checking trie-standardmap v0.12.2 [INFO] [stderr] error[E0463]: can't find crate for `reference_trie` [INFO] [stderr] --> src/lib.rs:43:1 [INFO] [stderr] | [INFO] [stderr] 43 | extern crate reference_trie; [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 `trie-db`. [INFO] [stderr] warning: build failed, waiting for other jobs to finish... [INFO] [stderr] error[E0597]: `keys` does not live long enough [INFO] [stderr] --> benches/bench.rs:36:22 [INFO] [stderr] | [INFO] [stderr] 36 | let mixed: Vec<_> = keys.iter().zip(values.iter().rev()).map(|pair| { [INFO] [stderr] | ^^^^ borrowed value does not live long enough [INFO] [stderr] ... [INFO] [stderr] 44 | } [INFO] [stderr] | - borrowed value only lives until here [INFO] [stderr] | [INFO] [stderr] = note: borrowed value must be valid for the static lifetime... [INFO] [stderr] [INFO] [stderr] error[E0597]: `values` does not live long enough [INFO] [stderr] --> benches/bench.rs:36:38 [INFO] [stderr] | [INFO] [stderr] 36 | let mixed: Vec<_> = keys.iter().zip(values.iter().rev()).map(|pair| { [INFO] [stderr] | ^^^^^^ borrowed value does not live long enough [INFO] [stderr] ... [INFO] [stderr] 44 | } [INFO] [stderr] | - borrowed value only lives until here [INFO] [stderr] | [INFO] [stderr] = note: borrowed value must be valid for the static lifetime... [INFO] [stderr] [INFO] [stderr] error[E0373]: closure may outlive the current function, but it borrows `mixed`, which is owned by the current function [INFO] [stderr] --> benches/bench.rs:39:43 [INFO] [stderr] | [INFO] [stderr] 39 | b.bench_function("nibble_common_prefix", |b| b.iter(&mut ||{ [INFO] [stderr] | ^^^ may outlive borrowed value `mixed` [INFO] [stderr] 40 | for (left, right) in mixed.iter() { [INFO] [stderr] | ----- `mixed` is borrowed here [INFO] [stderr] help: to force the closure to take ownership of `mixed` (and any other referenced variables), use the `move` keyword [INFO] [stderr] | [INFO] [stderr] 39 | b.bench_function("nibble_common_prefix", move |b| b.iter(&mut ||{ [INFO] [stderr] | ^^^^^^^^ [INFO] [stderr] [INFO] [stderr] error: aborting due to 3 previous errors [INFO] [stderr] [INFO] [stderr] Some errors occurred: E0373, E0597. [INFO] [stderr] For more information about an error, try `rustc --explain E0373`. [INFO] [stderr] error: Could not compile `trie-db`. [INFO] [stderr] [INFO] [stderr] To learn more, run the command again with --verbose. [INFO] running `"docker" "inspect" "f1fcd116f886fab7f4858d3f99172c7b6d749ed618f81b2a7a9cb8d9c4053bcc"` [INFO] running `"docker" "rm" "-f" "f1fcd116f886fab7f4858d3f99172c7b6d749ed618f81b2a7a9cb8d9c4053bcc"` [INFO] [stdout] f1fcd116f886fab7f4858d3f99172c7b6d749ed618f81b2a7a9cb8d9c4053bcc