[INFO] fetching crate identified_vec 0.1.11...
[INFO] testing identified_vec-0.1.11 against try#c2e32f1c9652b13ed99608599c1e855462f421f3 for pr-146098-7
[INFO] extracting crate identified_vec 0.1.11 into /workspace/builds/worker-2-tc2/source
[INFO] started tweaking crates.io crate identified_vec 0.1.11
[INFO] finished tweaking crates.io crate identified_vec 0.1.11
[INFO] tweaked toml for crates.io crate identified_vec 0.1.11 written to /workspace/builds/worker-2-tc2/source/Cargo.toml
[INFO] validating manifest of crates.io crate identified_vec 0.1.11 on toolchain c2e32f1c9652b13ed99608599c1e855462f421f3
[INFO] running `Command { std: CARGO_HOME="/workspace/cargo-home" RUSTUP_HOME="/workspace/rustup-home" "/workspace/cargo-home/bin/cargo" "+c2e32f1c9652b13ed99608599c1e855462f421f3" "metadata" "--manifest-path" "Cargo.toml" "--no-deps", kill_on_drop: false }`
[INFO] running `Command { std: CARGO_HOME="/workspace/cargo-home" RUSTUP_HOME="/workspace/rustup-home" "/workspace/cargo-home/bin/cargo" "+c2e32f1c9652b13ed99608599c1e855462f421f3" "generate-lockfile" "--manifest-path" "Cargo.toml", kill_on_drop: false }`
[INFO] [stderr]     Updating crates.io index
[INFO] [stderr]      Locking 13 packages to latest compatible versions
[INFO] [stderr]       Adding thiserror v1.0.69 (available: v2.0.17)
[INFO] running `Command { std: CARGO_HOME="/workspace/cargo-home" RUSTUP_HOME="/workspace/rustup-home" "/workspace/cargo-home/bin/cargo" "+c2e32f1c9652b13ed99608599c1e855462f421f3" "fetch" "--manifest-path" "Cargo.toml", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-2-tc2/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-2-tc2/source:/opt/rustwide/workdir:ro,Z" "-v" "/var/lib/crater-agent-workspace/cargo-home:/opt/rustwide/cargo-home:ro,Z" "-v" "/var/lib/crater-agent-workspace/rustup-home:/opt/rustwide/rustup-home:ro,Z" "-e" "SOURCE_DIR=/opt/rustwide/workdir" "-e" "CARGO_TARGET_DIR=/opt/rustwide/target" "-e" "CARGO_HOME=/opt/rustwide/cargo-home" "-e" "RUSTUP_HOME=/opt/rustwide/rustup-home" "-w" "/opt/rustwide/workdir" "-m" "1610612736" "--user" "0:0" "--network" "none" "ghcr.io/rust-lang/crates-build-env/linux@sha256:4848fb76d95f26979359cc7e45710b1dbc8f3acb7aeedee7c460d7702230f228" "/opt/rustwide/cargo-home/bin/cargo" "+c2e32f1c9652b13ed99608599c1e855462f421f3" "metadata" "--no-deps" "--format-version=1", kill_on_drop: false }`
[INFO] [stdout] 5aca1bf4f6e6db6334fb00c8f9ebc3081c53a032d2ad45164a66f10ff9a583a4
[INFO] running `Command { std: "docker" "start" "-a" "5aca1bf4f6e6db6334fb00c8f9ebc3081c53a032d2ad45164a66f10ff9a583a4", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "inspect" "5aca1bf4f6e6db6334fb00c8f9ebc3081c53a032d2ad45164a66f10ff9a583a4", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "rm" "-f" "5aca1bf4f6e6db6334fb00c8f9ebc3081c53a032d2ad45164a66f10ff9a583a4", kill_on_drop: false }`
[INFO] [stdout] 5aca1bf4f6e6db6334fb00c8f9ebc3081c53a032d2ad45164a66f10ff9a583a4
[INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-2-tc2/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-2-tc2/source:/opt/rustwide/workdir:ro,Z" "-v" "/var/lib/crater-agent-workspace/cargo-home:/opt/rustwide/cargo-home:ro,Z" "-v" "/var/lib/crater-agent-workspace/rustup-home:/opt/rustwide/rustup-home:ro,Z" "-e" "SOURCE_DIR=/opt/rustwide/workdir" "-e" "CARGO_TARGET_DIR=/opt/rustwide/target" "-e" "CARGO_INCREMENTAL=0" "-e" "RUST_BACKTRACE=full" "-e" "RUSTFLAGS=--cap-lints=forbid" "-e" "RUSTDOCFLAGS=--cap-lints=forbid" "-e" "CARGO_HOME=/opt/rustwide/cargo-home" "-e" "RUSTUP_HOME=/opt/rustwide/rustup-home" "-w" "/opt/rustwide/workdir" "-m" "1610612736" "--user" "0:0" "--network" "none" "ghcr.io/rust-lang/crates-build-env/linux@sha256:4848fb76d95f26979359cc7e45710b1dbc8f3acb7aeedee7c460d7702230f228" "/opt/rustwide/cargo-home/bin/cargo" "+c2e32f1c9652b13ed99608599c1e855462f421f3" "build" "--frozen" "--message-format=json", kill_on_drop: false }`
[INFO] [stdout] 26b0f1d05d470977def6a9ff88930c142895a63f5101d8ddcbb57f53deb4fbd9
[INFO] running `Command { std: "docker" "start" "-a" "26b0f1d05d470977def6a9ff88930c142895a63f5101d8ddcbb57f53deb4fbd9", kill_on_drop: false }`
[INFO] [stderr]    Compiling identified_vec v0.1.11 (/opt/rustwide/workdir)
[INFO] [stdout] warning: unexpected `cfg` condition name: `tarpaulin_include`
[INFO] [stdout]    --> src/vec/identified_vec.rs:210:15
[INFO] [stdout]     |
[INFO] [stdout] 210 |     #[cfg(not(tarpaulin_include))] // false negative
[INFO] [stdout]     |               ^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = help: expected names are: `docsrs`, `feature`, and `test` and 31 more
[INFO] [stdout]     = help: consider using a Cargo feature instead
[INFO] [stdout]     = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]              [lints.rust]
[INFO] [stdout]              unexpected_cfgs = { level = "warn", check-cfg = ['cfg(tarpaulin_include)'] }
[INFO] [stdout]     = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(tarpaulin_include)");` to the top of the `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: `#[warn(unexpected_cfgs)]` on by default
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `tarpaulin_include`
[INFO] [stdout]    --> src/vec/identified_vec.rs:268:15
[INFO] [stdout]     |
[INFO] [stdout] 268 |     #[cfg(not(tarpaulin_include))] // false negative
[INFO] [stdout]     |               ^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead
[INFO] [stdout]     = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]              [lints.rust]
[INFO] [stdout]              unexpected_cfgs = { level = "warn", check-cfg = ['cfg(tarpaulin_include)'] }
[INFO] [stdout]     = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(tarpaulin_include)");` to the top of the `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `tarpaulin_include`
[INFO] [stdout]    --> src/vec/identified_vec.rs:541:15
[INFO] [stdout]     |
[INFO] [stdout] 541 |     #[cfg(not(tarpaulin_include))] // false negative
[INFO] [stdout]     |               ^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead
[INFO] [stdout]     = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]              [lints.rust]
[INFO] [stdout]              unexpected_cfgs = { level = "warn", check-cfg = ['cfg(tarpaulin_include)'] }
[INFO] [stdout]     = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(tarpaulin_include)");` to the top of the `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `tarpaulin_include`
[INFO] [stdout]    --> src/vec/identified_vec.rs:607:15
[INFO] [stdout]     |
[INFO] [stdout] 607 |     #[cfg(not(tarpaulin_include))] // false negative
[INFO] [stdout]     |               ^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead
[INFO] [stdout]     = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]              [lints.rust]
[INFO] [stdout]              unexpected_cfgs = { level = "warn", check-cfg = ['cfg(tarpaulin_include)'] }
[INFO] [stdout]     = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(tarpaulin_include)");` to the top of the `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `tarpaulin_include`
[INFO] [stdout]    --> src/vec/identified_vec.rs:802:15
[INFO] [stdout]     |
[INFO] [stdout] 802 |     #[cfg(not(tarpaulin_include))] // false negative
[INFO] [stdout]     |               ^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead
[INFO] [stdout]     = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]              [lints.rust]
[INFO] [stdout]              unexpected_cfgs = { level = "warn", check-cfg = ['cfg(tarpaulin_include)'] }
[INFO] [stdout]     = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(tarpaulin_include)");` to the top of the `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unused import: `newtype_identified_vec_of::*`
[INFO] [stdout]   --> src/vec_of/mod.rs:14:9
[INFO] [stdout]    |
[INFO] [stdout] 14 | pub use newtype_identified_vec_of::*;
[INFO] [stdout]    |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: `#[warn(unused_imports)]` (part of `#[warn(unused)]`) on by default
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unused import: `primitives_identifiable::*`
[INFO] [stdout]   --> src/vec_of/mod.rs:17:9
[INFO] [stdout]    |
[INFO] [stdout] 17 | pub use primitives_identifiable::*;
[INFO] [stdout]    |         ^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing
[INFO] [stdout]    --> src/vec/identified_vec.rs:692:13
[INFO] [stdout]     |
[INFO] [stdout] 692 |     fn iter(&self) -> IdentifiedVecIterator<I, E> {
[INFO] [stdout]     |             ^^^^^     ^^^^^^^^^^^^^^^^^^^^^^^^^^^ the same lifetime is hidden here
[INFO] [stdout]     |             |
[INFO] [stdout]     |             the lifetime is elided here
[INFO] [stdout]     |
[INFO] [stdout]     = help: the same lifetime is referred to in inconsistent ways, making the signature confusing
[INFO] [stdout]     = note: `#[warn(mismatched_lifetime_syntaxes)]` on by default
[INFO] [stdout] help: use `'_` for type paths
[INFO] [stdout]     |
[INFO] [stdout] 692 |     fn iter(&self) -> IdentifiedVecIterator<'_, I, E> {
[INFO] [stdout]     |                                             +++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing
[INFO] [stdout]    --> src/vec/is_identified_vec.rs:268:13
[INFO] [stdout]     |
[INFO] [stdout] 268 |     fn iter(&self) -> IdentifiedVecIterator<ID, Element>;
[INFO] [stdout]     |             ^^^^^     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ the same lifetime is hidden here
[INFO] [stdout]     |             |
[INFO] [stdout]     |             the lifetime is elided here
[INFO] [stdout]     |
[INFO] [stdout]     = help: the same lifetime is referred to in inconsistent ways, making the signature confusing
[INFO] [stdout] help: use `'_` for type paths
[INFO] [stdout]     |
[INFO] [stdout] 268 |     fn iter(&self) -> IdentifiedVecIterator<'_, ID, Element>;
[INFO] [stdout]     |                                             +++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing
[INFO] [stdout]    --> src/vec_of/is_identified_vec_of_via.rs:226:13
[INFO] [stdout]     |
[INFO] [stdout] 226 |     fn iter(&self) -> IdentifiedVecIterator<<Element as Identifiable>::ID, Element> {
[INFO] [stdout]     |             ^^^^^     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ the same lifetime is hidden here
[INFO] [stdout]     |             |
[INFO] [stdout]     |             the lifetime is elided here
[INFO] [stdout]     |
[INFO] [stdout]     = help: the same lifetime is referred to in inconsistent ways, making the signature confusing
[INFO] [stdout] help: use `'_` for type paths
[INFO] [stdout]     |
[INFO] [stdout] 226 |     fn iter(&self) -> IdentifiedVecIterator<'_, <Element as Identifiable>::ID, Element> {
[INFO] [stdout]     |                                             +++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stderr]     Finished `dev` profile [unoptimized + debuginfo] target(s) in 0.38s
[INFO] running `Command { std: "docker" "inspect" "26b0f1d05d470977def6a9ff88930c142895a63f5101d8ddcbb57f53deb4fbd9", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "rm" "-f" "26b0f1d05d470977def6a9ff88930c142895a63f5101d8ddcbb57f53deb4fbd9", kill_on_drop: false }`
[INFO] [stdout] 26b0f1d05d470977def6a9ff88930c142895a63f5101d8ddcbb57f53deb4fbd9
[INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-2-tc2/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-2-tc2/source:/opt/rustwide/workdir:ro,Z" "-v" "/var/lib/crater-agent-workspace/cargo-home:/opt/rustwide/cargo-home:ro,Z" "-v" "/var/lib/crater-agent-workspace/rustup-home:/opt/rustwide/rustup-home:ro,Z" "-e" "SOURCE_DIR=/opt/rustwide/workdir" "-e" "CARGO_TARGET_DIR=/opt/rustwide/target" "-e" "CARGO_INCREMENTAL=0" "-e" "RUST_BACKTRACE=full" "-e" "RUSTFLAGS=--cap-lints=forbid" "-e" "RUSTDOCFLAGS=--cap-lints=forbid" "-e" "CARGO_HOME=/opt/rustwide/cargo-home" "-e" "RUSTUP_HOME=/opt/rustwide/rustup-home" "-w" "/opt/rustwide/workdir" "-m" "1610612736" "--user" "0:0" "--network" "none" "ghcr.io/rust-lang/crates-build-env/linux@sha256:4848fb76d95f26979359cc7e45710b1dbc8f3acb7aeedee7c460d7702230f228" "/opt/rustwide/cargo-home/bin/cargo" "+c2e32f1c9652b13ed99608599c1e855462f421f3" "test" "--frozen" "--no-run" "--message-format=json", kill_on_drop: false }`
[INFO] [stdout] d979b0fd3263e259732a8f490019e3fd00a51c05a70170ec585b4a20c9094e8d
[INFO] running `Command { std: "docker" "start" "-a" "d979b0fd3263e259732a8f490019e3fd00a51c05a70170ec585b4a20c9094e8d", kill_on_drop: false }`
[INFO] [stderr]    Compiling identified_vec v0.1.11 (/opt/rustwide/workdir)
[INFO] [stdout] warning: unexpected `cfg` condition name: `tarpaulin_include`
[INFO] [stdout]    --> src/vec/identified_vec.rs:210:15
[INFO] [stdout]     |
[INFO] [stdout] 210 |     #[cfg(not(tarpaulin_include))] // false negative
[INFO] [stdout]     |               ^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = help: expected names are: `docsrs`, `feature`, and `test` and 31 more
[INFO] [stdout]     = help: consider using a Cargo feature instead
[INFO] [stdout]     = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]              [lints.rust]
[INFO] [stdout]              unexpected_cfgs = { level = "warn", check-cfg = ['cfg(tarpaulin_include)'] }
[INFO] [stdout]     = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(tarpaulin_include)");` to the top of the `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: `#[warn(unexpected_cfgs)]` on by default
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `tarpaulin_include`
[INFO] [stdout]    --> src/vec/identified_vec.rs:268:15
[INFO] [stdout]     |
[INFO] [stdout] 268 |     #[cfg(not(tarpaulin_include))] // false negative
[INFO] [stdout]     |               ^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead
[INFO] [stdout]     = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]              [lints.rust]
[INFO] [stdout]              unexpected_cfgs = { level = "warn", check-cfg = ['cfg(tarpaulin_include)'] }
[INFO] [stdout]     = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(tarpaulin_include)");` to the top of the `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `tarpaulin_include`
[INFO] [stdout]    --> src/vec/identified_vec.rs:541:15
[INFO] [stdout]     |
[INFO] [stdout] 541 |     #[cfg(not(tarpaulin_include))] // false negative
[INFO] [stdout]     |               ^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead
[INFO] [stdout]     = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]              [lints.rust]
[INFO] [stdout]              unexpected_cfgs = { level = "warn", check-cfg = ['cfg(tarpaulin_include)'] }
[INFO] [stdout]     = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(tarpaulin_include)");` to the top of the `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `tarpaulin_include`
[INFO] [stdout]    --> src/vec/identified_vec.rs:607:15
[INFO] [stdout]     |
[INFO] [stdout] 607 |     #[cfg(not(tarpaulin_include))] // false negative
[INFO] [stdout]     |               ^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead
[INFO] [stdout]     = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]              [lints.rust]
[INFO] [stdout]              unexpected_cfgs = { level = "warn", check-cfg = ['cfg(tarpaulin_include)'] }
[INFO] [stdout]     = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(tarpaulin_include)");` to the top of the `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `tarpaulin_include`
[INFO] [stdout]    --> src/vec/identified_vec.rs:802:15
[INFO] [stdout]     |
[INFO] [stdout] 802 |     #[cfg(not(tarpaulin_include))] // false negative
[INFO] [stdout]     |               ^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead
[INFO] [stdout]     = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]              [lints.rust]
[INFO] [stdout]              unexpected_cfgs = { level = "warn", check-cfg = ['cfg(tarpaulin_include)'] }
[INFO] [stdout]     = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(tarpaulin_include)");` to the top of the `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unused import: `newtype_identified_vec_of::*`
[INFO] [stdout]   --> src/vec_of/mod.rs:14:9
[INFO] [stdout]    |
[INFO] [stdout] 14 | pub use newtype_identified_vec_of::*;
[INFO] [stdout]    |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: `#[warn(unused_imports)]` (part of `#[warn(unused)]`) on by default
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unused import: `primitives_identifiable::*`
[INFO] [stdout]   --> src/vec_of/mod.rs:17:9
[INFO] [stdout]    |
[INFO] [stdout] 17 | pub use primitives_identifiable::*;
[INFO] [stdout]    |         ^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing
[INFO] [stdout]    --> src/vec/identified_vec.rs:692:13
[INFO] [stdout]     |
[INFO] [stdout] 692 |     fn iter(&self) -> IdentifiedVecIterator<I, E> {
[INFO] [stdout]     |             ^^^^^     ^^^^^^^^^^^^^^^^^^^^^^^^^^^ the same lifetime is hidden here
[INFO] [stdout]     |             |
[INFO] [stdout]     |             the lifetime is elided here
[INFO] [stdout]     |
[INFO] [stdout]     = help: the same lifetime is referred to in inconsistent ways, making the signature confusing
[INFO] [stdout]     = note: `#[warn(mismatched_lifetime_syntaxes)]` on by default
[INFO] [stdout] help: use `'_` for type paths
[INFO] [stdout]     |
[INFO] [stdout] 692 |     fn iter(&self) -> IdentifiedVecIterator<'_, I, E> {
[INFO] [stdout]     |                                             +++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing
[INFO] [stdout]    --> src/vec/is_identified_vec.rs:268:13
[INFO] [stdout]     |
[INFO] [stdout] 268 |     fn iter(&self) -> IdentifiedVecIterator<ID, Element>;
[INFO] [stdout]     |             ^^^^^     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ the same lifetime is hidden here
[INFO] [stdout]     |             |
[INFO] [stdout]     |             the lifetime is elided here
[INFO] [stdout]     |
[INFO] [stdout]     = help: the same lifetime is referred to in inconsistent ways, making the signature confusing
[INFO] [stdout] help: use `'_` for type paths
[INFO] [stdout]     |
[INFO] [stdout] 268 |     fn iter(&self) -> IdentifiedVecIterator<'_, ID, Element>;
[INFO] [stdout]     |                                             +++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing
[INFO] [stdout]    --> src/vec_of/is_identified_vec_of_via.rs:226:13
[INFO] [stdout]     |
[INFO] [stdout] 226 |     fn iter(&self) -> IdentifiedVecIterator<<Element as Identifiable>::ID, Element> {
[INFO] [stdout]     |             ^^^^^     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ the same lifetime is hidden here
[INFO] [stdout]     |             |
[INFO] [stdout]     |             the lifetime is elided here
[INFO] [stdout]     |
[INFO] [stdout]     = help: the same lifetime is referred to in inconsistent ways, making the signature confusing
[INFO] [stdout] help: use `'_` for type paths
[INFO] [stdout]     |
[INFO] [stdout] 226 |     fn iter(&self) -> IdentifiedVecIterator<'_, <Element as Identifiable>::ID, Element> {
[INFO] [stdout]     |                                             +++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `tarpaulin_include`
[INFO] [stdout]    --> src/vec/identified_vec.rs:210:15
[INFO] [stdout]     |
[INFO] [stdout] 210 |     #[cfg(not(tarpaulin_include))] // false negative
[INFO] [stdout]     |               ^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = help: expected names are: `docsrs`, `feature`, and `test` and 31 more
[INFO] [stdout]     = help: consider using a Cargo feature instead
[INFO] [stdout]     = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]              [lints.rust]
[INFO] [stdout]              unexpected_cfgs = { level = "warn", check-cfg = ['cfg(tarpaulin_include)'] }
[INFO] [stdout]     = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(tarpaulin_include)");` to the top of the `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: `#[warn(unexpected_cfgs)]` on by default
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `tarpaulin_include`
[INFO] [stdout]    --> src/vec/identified_vec.rs:268:15
[INFO] [stdout]     |
[INFO] [stdout] 268 |     #[cfg(not(tarpaulin_include))] // false negative
[INFO] [stdout]     |               ^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead
[INFO] [stdout]     = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]              [lints.rust]
[INFO] [stdout]              unexpected_cfgs = { level = "warn", check-cfg = ['cfg(tarpaulin_include)'] }
[INFO] [stdout]     = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(tarpaulin_include)");` to the top of the `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `tarpaulin_include`
[INFO] [stdout]    --> src/vec/identified_vec.rs:541:15
[INFO] [stdout]     |
[INFO] [stdout] 541 |     #[cfg(not(tarpaulin_include))] // false negative
[INFO] [stdout]     |               ^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead
[INFO] [stdout]     = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]              [lints.rust]
[INFO] [stdout]              unexpected_cfgs = { level = "warn", check-cfg = ['cfg(tarpaulin_include)'] }
[INFO] [stdout]     = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(tarpaulin_include)");` to the top of the `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `tarpaulin_include`
[INFO] [stdout]    --> src/vec/identified_vec.rs:607:15
[INFO] [stdout]     |
[INFO] [stdout] 607 |     #[cfg(not(tarpaulin_include))] // false negative
[INFO] [stdout]     |               ^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead
[INFO] [stdout]     = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]              [lints.rust]
[INFO] [stdout]              unexpected_cfgs = { level = "warn", check-cfg = ['cfg(tarpaulin_include)'] }
[INFO] [stdout]     = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(tarpaulin_include)");` to the top of the `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `tarpaulin_include`
[INFO] [stdout]    --> src/vec/identified_vec.rs:802:15
[INFO] [stdout]     |
[INFO] [stdout] 802 |     #[cfg(not(tarpaulin_include))] // false negative
[INFO] [stdout]     |               ^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead
[INFO] [stdout]     = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]              [lints.rust]
[INFO] [stdout]              unexpected_cfgs = { level = "warn", check-cfg = ['cfg(tarpaulin_include)'] }
[INFO] [stdout]     = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(tarpaulin_include)");` to the top of the `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unused import: `newtype_identified_vec_of::*`
[INFO] [stdout]   --> src/vec_of/mod.rs:14:9
[INFO] [stdout]    |
[INFO] [stdout] 14 | pub use newtype_identified_vec_of::*;
[INFO] [stdout]    |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: `#[warn(unused_imports)]` (part of `#[warn(unused)]`) on by default
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unused import: `primitives_identifiable::*`
[INFO] [stdout]   --> src/vec_of/mod.rs:17:9
[INFO] [stdout]    |
[INFO] [stdout] 17 | pub use primitives_identifiable::*;
[INFO] [stdout]    |         ^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0432]: unresolved import `identified_vec::IdentifiedVecOfSerdeFailure`
[INFO] [stdout]  --> tests/tests.rs:5:22
[INFO] [stdout]   |
[INFO] [stdout] 5 |     IdentifiedVecOf, IdentifiedVecOfSerdeFailure, IsIdentifiedVec, IsIdentifiedVecOf, ItemsCloned,
[INFO] [stdout]   |                      ^^^^^^^^^^^^^^^^^^^^^^^^^^^ no `IdentifiedVecOfSerdeFailure` in the root
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `tarpaulin_include`
[INFO] [stdout]   --> tests/tests.rs:54:1
[INFO] [stdout]    |
[INFO] [stdout] 54 | newtype_identified_vec!(of: u32, named: SUT);
[INFO] [stdout]    | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = help: expected names are: `docsrs`, `feature`, and `test` and 31 more
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `newtype_identified_vec` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the macro `newtype_identified_vec` may come from an old version of the `identified_vec` crate, try updating your dependency with `cargo update -p identified_vec`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: `#[warn(unexpected_cfgs)]` on by default
[INFO] [stdout]    = note: this warning originates in the macro `newtype_identified_vec` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `tarpaulin_include`
[INFO] [stdout]   --> tests/tests.rs:55:1
[INFO] [stdout]    |
[INFO] [stdout] 55 | newtype_identified_vec!(of: User, named: Users);
[INFO] [stdout]    | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `newtype_identified_vec` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the macro `newtype_identified_vec` may come from an old version of the `identified_vec` crate, try updating your dependency with `cargo update -p identified_vec`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `newtype_identified_vec` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `tarpaulin_include`
[INFO] [stdout]    --> tests/tests.rs:572:5
[INFO] [stdout]     |
[INFO] [stdout] 572 |     newtype_identified_vec!(of: u32, named: Ints);
[INFO] [stdout]     |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `newtype_identified_vec` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `newtype_identified_vec` may come from an old version of the `identified_vec` crate, try updating your dependency with `cargo update -p identified_vec`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `newtype_identified_vec` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `tarpaulin_include`
[INFO] [stdout]    --> tests/tests.rs:633:5
[INFO] [stdout]     |
[INFO] [stdout] 633 |     newtype_identified_vec!(of: Foo, named: SUT);
[INFO] [stdout]     |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `newtype_identified_vec` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `newtype_identified_vec` may come from an old version of the `identified_vec` crate, try updating your dependency with `cargo update -p identified_vec`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `newtype_identified_vec` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `tarpaulin_include`
[INFO] [stdout]    --> tests/tests.rs:715:5
[INFO] [stdout]     |
[INFO] [stdout] 715 |     newtype_identified_vec!(of: User, named: CollectionOfUsers);
[INFO] [stdout]     |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `newtype_identified_vec` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `newtype_identified_vec` may come from an old version of the `identified_vec` crate, try updating your dependency with `cargo update -p identified_vec`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `newtype_identified_vec` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0599]: the function or associated item `serialize` exists for struct `IdentifiedVec<_, _>`, but its trait bounds were not satisfied
[INFO] [stdout]    --> tests/tests.rs:54:1
[INFO] [stdout]     |
[INFO] [stdout]  54 | newtype_identified_vec!(of: u32, named: SUT);
[INFO] [stdout]     | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ function or associated item cannot be called on `IdentifiedVec<_, _>` due to unsatisfied trait bounds
[INFO] [stdout]     |
[INFO] [stdout]    ::: /opt/rustwide/workdir/src/vec/identified_vec.rs:161:1
[INFO] [stdout]     |
[INFO] [stdout] 161 | pub struct IdentifiedVec<I, E>
[INFO] [stdout]     | ------------------------------ doesn't satisfy `IdentifiedVec<_, _>: Serialize`
[INFO] [stdout]     |
[INFO] [stdout]     = note: the following trait bounds were not satisfied:
[INFO] [stdout]             `IdentifiedVec<_, _>: Serialize`
[INFO] [stdout]             which is required by `&IdentifiedVec<_, _>: Serialize`
[INFO] [stdout]             `IdentifiedVec<_, _>: Serialize`
[INFO] [stdout]             which is required by `&mut IdentifiedVec<_, _>: Serialize`
[INFO] [stdout]     = note: this error originates in the macro `newtype_identified_vec` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0599]: no function or associated item named `deserialize` found for struct `IdentifiedVec<I, E>` in the current scope
[INFO] [stdout]   --> tests/tests.rs:54:1
[INFO] [stdout]    |
[INFO] [stdout] 54 | newtype_identified_vec!(of: u32, named: SUT);
[INFO] [stdout]    | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ function or associated item not found in `IdentifiedVec<u32, u32>`
[INFO] [stdout]    |
[INFO] [stdout]    = note: this error originates in the macro `newtype_identified_vec` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0599]: the function or associated item `serialize` exists for struct `IdentifiedVec<_, _>`, but its trait bounds were not satisfied
[INFO] [stdout]    --> tests/tests.rs:55:1
[INFO] [stdout]     |
[INFO] [stdout]  55 | newtype_identified_vec!(of: User, named: Users);
[INFO] [stdout]     | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ function or associated item cannot be called on `IdentifiedVec<_, _>` due to unsatisfied trait bounds
[INFO] [stdout]     |
[INFO] [stdout]    ::: /opt/rustwide/workdir/src/vec/identified_vec.rs:161:1
[INFO] [stdout]     |
[INFO] [stdout] 161 | pub struct IdentifiedVec<I, E>
[INFO] [stdout]     | ------------------------------ doesn't satisfy `IdentifiedVec<_, _>: Serialize`
[INFO] [stdout]     |
[INFO] [stdout]     = note: the following trait bounds were not satisfied:
[INFO] [stdout]             `IdentifiedVec<_, _>: Serialize`
[INFO] [stdout]             which is required by `&IdentifiedVec<_, _>: Serialize`
[INFO] [stdout]             `IdentifiedVec<_, _>: Serialize`
[INFO] [stdout]             which is required by `&mut IdentifiedVec<_, _>: Serialize`
[INFO] [stdout]     = note: this error originates in the macro `newtype_identified_vec` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0599]: no function or associated item named `deserialize` found for struct `IdentifiedVec<I, E>` in the current scope
[INFO] [stdout]   --> tests/tests.rs:55:1
[INFO] [stdout]    |
[INFO] [stdout] 55 | newtype_identified_vec!(of: User, named: Users);
[INFO] [stdout]    | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ function or associated item not found in `IdentifiedVec<u16, User>`
[INFO] [stdout]    |
[INFO] [stdout]    = note: this error originates in the macro `newtype_identified_vec` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing
[INFO] [stdout]    --> src/vec/identified_vec.rs:692:13
[INFO] [stdout]     |
[INFO] [stdout] 692 |     fn iter(&self) -> IdentifiedVecIterator<I, E> {
[INFO] [stdout]     |             ^^^^^     ^^^^^^^^^^^^^^^^^^^^^^^^^^^ the same lifetime is hidden here
[INFO] [stdout]     |             |
[INFO] [stdout]     |             the lifetime is elided here
[INFO] [stdout]     |
[INFO] [stdout]     = help: the same lifetime is referred to in inconsistent ways, making the signature confusing
[INFO] [stdout]     = note: `#[warn(mismatched_lifetime_syntaxes)]` on by default
[INFO] [stdout] help: use `'_` for type paths
[INFO] [stdout]     |
[INFO] [stdout] 692 |     fn iter(&self) -> IdentifiedVecIterator<'_, I, E> {
[INFO] [stdout]     |                                             +++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing
[INFO] [stdout]    --> src/vec/is_identified_vec.rs:268:13
[INFO] [stdout]     |
[INFO] [stdout] 268 |     fn iter(&self) -> IdentifiedVecIterator<ID, Element>;
[INFO] [stdout]     |             ^^^^^     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ the same lifetime is hidden here
[INFO] [stdout]     |             |
[INFO] [stdout]     |             the lifetime is elided here
[INFO] [stdout]     |
[INFO] [stdout]     = help: the same lifetime is referred to in inconsistent ways, making the signature confusing
[INFO] [stdout] help: use `'_` for type paths
[INFO] [stdout]     |
[INFO] [stdout] 268 |     fn iter(&self) -> IdentifiedVecIterator<'_, ID, Element>;
[INFO] [stdout]     |                                             +++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing
[INFO] [stdout]    --> src/vec_of/is_identified_vec_of_via.rs:226:13
[INFO] [stdout]     |
[INFO] [stdout] 226 |     fn iter(&self) -> IdentifiedVecIterator<<Element as Identifiable>::ID, Element> {
[INFO] [stdout]     |             ^^^^^     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ the same lifetime is hidden here
[INFO] [stdout]     |             |
[INFO] [stdout]     |             the lifetime is elided here
[INFO] [stdout]     |
[INFO] [stdout]     = help: the same lifetime is referred to in inconsistent ways, making the signature confusing
[INFO] [stdout] help: use `'_` for type paths
[INFO] [stdout]     |
[INFO] [stdout] 226 |     fn iter(&self) -> IdentifiedVecIterator<'_, <Element as Identifiable>::ID, Element> {
[INFO] [stdout]     |                                             +++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0599]: the function or associated item `serialize` exists for struct `IdentifiedVec<_, _>`, but its trait bounds were not satisfied
[INFO] [stdout]    --> tests/tests.rs:572:5
[INFO] [stdout]     |
[INFO] [stdout] 572 |     newtype_identified_vec!(of: u32, named: Ints);
[INFO] [stdout]     |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ function or associated item cannot be called on `IdentifiedVec<_, _>` due to unsatisfied trait bounds
[INFO] [stdout]     |
[INFO] [stdout]    ::: /opt/rustwide/workdir/src/vec/identified_vec.rs:161:1
[INFO] [stdout]     |
[INFO] [stdout] 161 | pub struct IdentifiedVec<I, E>
[INFO] [stdout]     | ------------------------------ doesn't satisfy `IdentifiedVec<_, _>: Serialize`
[INFO] [stdout]     |
[INFO] [stdout]     = note: the following trait bounds were not satisfied:
[INFO] [stdout]             `IdentifiedVec<_, _>: Serialize`
[INFO] [stdout]             which is required by `&IdentifiedVec<_, _>: Serialize`
[INFO] [stdout]             `IdentifiedVec<_, _>: Serialize`
[INFO] [stdout]             which is required by `&mut IdentifiedVec<_, _>: Serialize`
[INFO] [stdout]     = note: this error originates in the macro `newtype_identified_vec` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0599]: no function or associated item named `deserialize` found for struct `IdentifiedVec<I, E>` in the current scope
[INFO] [stdout]    --> tests/tests.rs:572:5
[INFO] [stdout]     |
[INFO] [stdout] 572 |     newtype_identified_vec!(of: u32, named: Ints);
[INFO] [stdout]     |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ function or associated item not found in `IdentifiedVec<u32, u32>`
[INFO] [stdout]     |
[INFO] [stdout]     = note: this error originates in the macro `newtype_identified_vec` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0599]: the function or associated item `serialize` exists for struct `IdentifiedVec<_, _>`, but its trait bounds were not satisfied
[INFO] [stdout]    --> tests/tests.rs:633:5
[INFO] [stdout]     |
[INFO] [stdout] 633 |     newtype_identified_vec!(of: Foo, named: SUT);
[INFO] [stdout]     |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ function or associated item cannot be called on `IdentifiedVec<_, _>` due to unsatisfied trait bounds
[INFO] [stdout]     |
[INFO] [stdout]    ::: /opt/rustwide/workdir/src/vec/identified_vec.rs:161:1
[INFO] [stdout]     |
[INFO] [stdout] 161 | pub struct IdentifiedVec<I, E>
[INFO] [stdout]     | ------------------------------ doesn't satisfy `IdentifiedVec<_, _>: Serialize`
[INFO] [stdout]     |
[INFO] [stdout]     = note: the following trait bounds were not satisfied:
[INFO] [stdout]             `IdentifiedVec<_, _>: Serialize`
[INFO] [stdout]             which is required by `&IdentifiedVec<_, _>: Serialize`
[INFO] [stdout]             `IdentifiedVec<_, _>: Serialize`
[INFO] [stdout]             which is required by `&mut IdentifiedVec<_, _>: Serialize`
[INFO] [stdout]     = note: this error originates in the macro `newtype_identified_vec` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0599]: no function or associated item named `deserialize` found for struct `IdentifiedVec<I, E>` in the current scope
[INFO] [stdout]    --> tests/tests.rs:633:5
[INFO] [stdout]     |
[INFO] [stdout] 633 |     newtype_identified_vec!(of: Foo, named: SUT);
[INFO] [stdout]     |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ function or associated item not found in `IdentifiedVec<&'static str, Foo>`
[INFO] [stdout]     |
[INFO] [stdout]     = note: this error originates in the macro `newtype_identified_vec` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0599]: the function or associated item `serialize` exists for struct `IdentifiedVec<_, _>`, but its trait bounds were not satisfied
[INFO] [stdout]    --> tests/tests.rs:715:5
[INFO] [stdout]     |
[INFO] [stdout] 715 |     newtype_identified_vec!(of: User, named: CollectionOfUsers);
[INFO] [stdout]     |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ function or associated item cannot be called on `IdentifiedVec<_, _>` due to unsatisfied trait bounds
[INFO] [stdout]     |
[INFO] [stdout]    ::: /opt/rustwide/workdir/src/vec/identified_vec.rs:161:1
[INFO] [stdout]     |
[INFO] [stdout] 161 | pub struct IdentifiedVec<I, E>
[INFO] [stdout]     | ------------------------------ doesn't satisfy `IdentifiedVec<_, _>: Serialize`
[INFO] [stdout]     |
[INFO] [stdout]     = note: the following trait bounds were not satisfied:
[INFO] [stdout]             `IdentifiedVec<_, _>: Serialize`
[INFO] [stdout]             which is required by `&IdentifiedVec<_, _>: Serialize`
[INFO] [stdout]             `IdentifiedVec<_, _>: Serialize`
[INFO] [stdout]             which is required by `&mut IdentifiedVec<_, _>: Serialize`
[INFO] [stdout]     = note: this error originates in the macro `newtype_identified_vec` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0599]: no function or associated item named `deserialize` found for struct `IdentifiedVec<I, E>` in the current scope
[INFO] [stdout]    --> tests/tests.rs:715:5
[INFO] [stdout]     |
[INFO] [stdout] 715 |     newtype_identified_vec!(of: User, named: CollectionOfUsers);
[INFO] [stdout]     |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ function or associated item not found in `IdentifiedVec<u16, User>`
[INFO] [stdout]     |
[INFO] [stdout]     = note: this error originates in the macro `newtype_identified_vec` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] Some errors have detailed explanations: E0432, E0599.
[INFO] [stdout] 
[INFO] [stdout] For more information about an error, try `rustc --explain E0432`.
[INFO] [stdout] 
[INFO] [stderr] error: could not compile `identified_vec` (test "tests") due to 11 previous errors; 5 warnings emitted
[INFO] running `Command { std: "docker" "inspect" "d979b0fd3263e259732a8f490019e3fd00a51c05a70170ec585b4a20c9094e8d", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "rm" "-f" "d979b0fd3263e259732a8f490019e3fd00a51c05a70170ec585b4a20c9094e8d", kill_on_drop: false }`
[INFO] [stdout] d979b0fd3263e259732a8f490019e3fd00a51c05a70170ec585b4a20c9094e8d
