[INFO] fetching crate identified_vec 0.1.11...
[INFO] checking identified_vec-0.1.11 against master#39cb3386ddc6c71657418be28dbb3987eea4aa4b for pr-133536
[INFO] extracting crate identified_vec 0.1.11 into /workspace/builds/worker-4-tc1/source
[INFO] validating manifest of crates.io crate identified_vec 0.1.11 on toolchain 39cb3386ddc6c71657418be28dbb3987eea4aa4b
[INFO] running `Command { std: CARGO_HOME="/workspace/cargo-home" RUSTUP_HOME="/workspace/rustup-home" "/workspace/cargo-home/bin/cargo" "+39cb3386ddc6c71657418be28dbb3987eea4aa4b" "metadata" "--manifest-path" "Cargo.toml" "--no-deps", kill_on_drop: false }`
[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-4-tc1/source/Cargo.toml
[INFO] running `Command { std: CARGO_HOME="/workspace/cargo-home" RUSTUP_HOME="/workspace/rustup-home" "/workspace/cargo-home/bin/cargo" "+39cb3386ddc6c71657418be28dbb3987eea4aa4b" "generate-lockfile" "--manifest-path" "Cargo.toml", kill_on_drop: false }`
[INFO] [stderr]     Updating crates.io index
[INFO] [stderr]      Locking 12 packages to latest compatible versions
[INFO] [stderr]       Adding thiserror v1.0.69 (available: v2.0.3)
[INFO] running `Command { std: CARGO_HOME="/workspace/cargo-home" RUSTUP_HOME="/workspace/rustup-home" "/workspace/cargo-home/bin/cargo" "+39cb3386ddc6c71657418be28dbb3987eea4aa4b" "fetch" "--manifest-path" "Cargo.toml", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-4-tc1/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-4-tc1/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:4a844ea9eb2546a2d2c7022eacef16ef2e8229c7fbb2c7d4d55a9ceca922f72d" "/opt/rustwide/cargo-home/bin/cargo" "+39cb3386ddc6c71657418be28dbb3987eea4aa4b" "metadata" "--no-deps" "--format-version=1", kill_on_drop: false }`
[INFO] [stdout] 868e85705e7687e7ab5d2c951918f32c61abfbb779ab2092ee94bd88c6abfaea
[INFO] running `Command { std: "docker" "start" "-a" "868e85705e7687e7ab5d2c951918f32c61abfbb779ab2092ee94bd88c6abfaea", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "inspect" "868e85705e7687e7ab5d2c951918f32c61abfbb779ab2092ee94bd88c6abfaea", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "rm" "-f" "868e85705e7687e7ab5d2c951918f32c61abfbb779ab2092ee94bd88c6abfaea", kill_on_drop: false }`
[INFO] [stdout] 868e85705e7687e7ab5d2c951918f32c61abfbb779ab2092ee94bd88c6abfaea
[INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-4-tc1/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-4-tc1/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:4a844ea9eb2546a2d2c7022eacef16ef2e8229c7fbb2c7d4d55a9ceca922f72d" "/opt/rustwide/cargo-home/bin/cargo" "+39cb3386ddc6c71657418be28dbb3987eea4aa4b" "check" "--frozen" "--all" "--all-targets" "--message-format=json", kill_on_drop: false }`
[INFO] [stdout] 76cb7bdbb563663ce5e03bacc18a7bc62dd9ad966398d543cd90158cdf117a90
[INFO] running `Command { std: "docker" "start" "-a" "76cb7bdbb563663ce5e03bacc18a7bc62dd9ad966398d543cd90158cdf117a90", kill_on_drop: false }`
[INFO] [stderr]    Compiling proc-macro2 v1.0.92
[INFO] [stderr]    Compiling serde v1.0.215
[INFO] [stderr]    Compiling thiserror v1.0.69
[INFO] [stderr]    Compiling quote v1.0.37
[INFO] [stderr]    Compiling syn v2.0.90
[INFO] [stderr]    Compiling serde_derive v1.0.215
[INFO] [stderr]    Compiling thiserror-impl v1.0.69
[INFO] [stderr]     Checking 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: `clippy`, `debug_assertions`, `doc`, `docsrs`, `doctest`, `feature`, `fmt_debug`, `miri`, `overflow_checks`, `panic`, `proc_macro`, `relocation_model`, `rustfmt`, `sanitize`, `sanitizer_cfi_generalize_pointers`, `sanitizer_cfi_normalize_integers`, `target_abi`, `target_arch`, `target_endian`, `target_env`, `target_family`, `target_feature`, `target_has_atomic`, `target_has_atomic_equal_alignment`, `target_has_atomic_load_store`, `target_os`, `target_pointer_width`, `target_thread_local`, `target_vendor`, `test`, `ub_checks`, `unix`, and `windows`
[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)]` 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] [stderr]     Checking serde_json v1.0.133
[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: `clippy`, `debug_assertions`, `doc`, `docsrs`, `doctest`, `feature`, `fmt_debug`, `miri`, `overflow_checks`, `panic`, `proc_macro`, `relocation_model`, `rustfmt`, `sanitize`, `sanitizer_cfi_generalize_pointers`, `sanitizer_cfi_normalize_integers`, `target_abi`, `target_arch`, `target_endian`, `target_env`, `target_family`, `target_feature`, `target_has_atomic`, `target_has_atomic_equal_alignment`, `target_has_atomic_load_store`, `target_os`, `target_pointer_width`, `target_thread_local`, `target_vendor`, `test`, `ub_checks`, `unix`, and `windows`
[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)]` 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: `clippy`, `debug_assertions`, `doc`, `docsrs`, `doctest`, `feature`, `fmt_debug`, `miri`, `overflow_checks`, `panic`, `proc_macro`, `relocation_model`, `rustfmt`, `sanitize`, `sanitizer_cfi_generalize_pointers`, `sanitizer_cfi_normalize_integers`, `target_abi`, `target_arch`, `target_endian`, `target_env`, `target_family`, `target_feature`, `target_has_atomic`, `target_has_atomic_equal_alignment`, `target_has_atomic_load_store`, `target_os`, `target_pointer_width`, `target_thread_local`, `target_vendor`, `test`, `ub_checks`, `unix`, and `windows`
[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]    = 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]    = 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: 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]     = 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: 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]     = 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: 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]     = 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: 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: for local types consider adding `#[derive(serde::Serialize)]` to your `IdentifiedVec<_, _>` type
[INFO] [stdout]     = note: for types from other crates check whether the crate offers a `serde` feature flag
[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` 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: for local types consider adding `#[derive(serde::Serialize)]` to your `IdentifiedVec<_, _>` type
[INFO] [stdout]     = note: for types from other crates check whether the crate offers a `serde` feature flag
[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` 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] 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: for local types consider adding `#[derive(serde::Serialize)]` to your `IdentifiedVec<_, _>` type
[INFO] [stdout]     = note: for types from other crates check whether the crate offers a `serde` feature flag
[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` 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: for local types consider adding `#[derive(serde::Serialize)]` to your `IdentifiedVec<_, _>` type
[INFO] [stdout]     = note: for types from other crates check whether the crate offers a `serde` feature flag
[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` 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<&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: for local types consider adding `#[derive(serde::Serialize)]` to your `IdentifiedVec<_, _>` type
[INFO] [stdout]     = note: for types from other crates check whether the crate offers a `serde` feature flag
[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` 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" "76cb7bdbb563663ce5e03bacc18a7bc62dd9ad966398d543cd90158cdf117a90", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "rm" "-f" "76cb7bdbb563663ce5e03bacc18a7bc62dd9ad966398d543cd90158cdf117a90", kill_on_drop: false }`
[INFO] [stdout] 76cb7bdbb563663ce5e03bacc18a7bc62dd9ad966398d543cd90158cdf117a90
