[INFO] fetching crate pnet_transport 0.35.0... [INFO] checking pnet_transport-0.35.0 against master#cf38b8e663f15db10ce49d7bbce02c99fc3dbc0c for pr-143170 [INFO] extracting crate pnet_transport 0.35.0 into /workspace/builds/worker-4-tc1/source [INFO] started tweaking crates.io crate pnet_transport 0.35.0 [INFO] finished tweaking crates.io crate pnet_transport 0.35.0 [INFO] tweaked toml for crates.io crate pnet_transport 0.35.0 written to /workspace/builds/worker-4-tc1/source/Cargo.toml [INFO] validating manifest of crates.io crate pnet_transport 0.35.0 on toolchain cf38b8e663f15db10ce49d7bbce02c99fc3dbc0c [INFO] running `Command { std: CARGO_HOME="/workspace/cargo-home" RUSTUP_HOME="/workspace/rustup-home" "/workspace/cargo-home/bin/cargo" "+cf38b8e663f15db10ce49d7bbce02c99fc3dbc0c" "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" "+cf38b8e663f15db10ce49d7bbce02c99fc3dbc0c" "generate-lockfile" "--manifest-path" "Cargo.toml", kill_on_drop: false }` [INFO] [stderr] Blocking waiting for file lock on package cache [INFO] [stderr] Updating crates.io index [INFO] [stderr] Blocking waiting for file lock on package cache [INFO] [stderr] Locking 20 packages to latest compatible versions [INFO] running `Command { std: CARGO_HOME="/workspace/cargo-home" RUSTUP_HOME="/workspace/rustup-home" "/workspace/cargo-home/bin/cargo" "+cf38b8e663f15db10ce49d7bbce02c99fc3dbc0c" "fetch" "--manifest-path" "Cargo.toml", kill_on_drop: false }` [INFO] [stderr] Blocking waiting for file lock on package cache [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:90999bfc7ae267e83380e433d8e61a7c072ca6729e92edbae886d3423b3a6f4c" "/opt/rustwide/cargo-home/bin/cargo" "+cf38b8e663f15db10ce49d7bbce02c99fc3dbc0c" "metadata" "--no-deps" "--format-version=1", kill_on_drop: false }` [INFO] [stdout] 5da2819bee4399e2efa7f53163e7996d67a696b0fd4f1e1f1cc7ed063728ff63 [INFO] running `Command { std: "docker" "start" "-a" "5da2819bee4399e2efa7f53163e7996d67a696b0fd4f1e1f1cc7ed063728ff63", kill_on_drop: false }` [INFO] running `Command { std: "docker" "inspect" "5da2819bee4399e2efa7f53163e7996d67a696b0fd4f1e1f1cc7ed063728ff63", kill_on_drop: false }` [INFO] running `Command { std: "docker" "rm" "-f" "5da2819bee4399e2efa7f53163e7996d67a696b0fd4f1e1f1cc7ed063728ff63", kill_on_drop: false }` [INFO] [stdout] 5da2819bee4399e2efa7f53163e7996d67a696b0fd4f1e1f1cc7ed063728ff63 [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:90999bfc7ae267e83380e433d8e61a7c072ca6729e92edbae886d3423b3a6f4c" "/opt/rustwide/cargo-home/bin/cargo" "+cf38b8e663f15db10ce49d7bbce02c99fc3dbc0c" "check" "--frozen" "--all" "--all-targets" "--message-format=json", kill_on_drop: false }` [INFO] [stdout] f2ade8c87b5a9de226125100c516c8b0c4b39140cde2b06161c22aef934e2428 [INFO] running `Command { std: "docker" "start" "-a" "f2ade8c87b5a9de226125100c516c8b0c4b39140cde2b06161c22aef934e2428", kill_on_drop: false }` [INFO] [stderr] Compiling regex-syntax v0.8.5 [INFO] [stderr] Checking no-std-net v0.6.0 [INFO] [stderr] Compiling syn v2.0.104 [INFO] [stderr] Checking pnet_sys v0.35.0 [INFO] [stderr] Checking pnet_base v0.35.0 [INFO] [stderr] Checking pnet_macros_support v0.35.0 [INFO] [stderr] Compiling regex-automata v0.4.9 [INFO] [stderr] Compiling regex v1.11.1 [INFO] [stderr] Compiling pnet_macros v0.35.0 [INFO] [stderr] Checking pnet_packet v0.35.0 [INFO] [stderr] Checking pnet_transport v0.35.0 (/opt/rustwide/workdir) [INFO] [stdout] error: lifetime flowing from input to output with different syntax can be confusing [INFO] [stdout] --> src/lib.rs:325:26 [INFO] [stdout] | [INFO] [stdout] 325 | pub fn $func(tr: &mut TransportReceiver) -> $iter { [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^ ----- the lifetime gets resolved as `'_` [INFO] [stdout] | | [INFO] [stdout] | this lifetime flows to the output [INFO] [stdout] ... [INFO] [stdout] 444 | transport_channel_iterator!(Ipv4Packet, Ipv4TransportChannelIterator, ipv4_packet_iter); [INFO] [stdout] | --------------------------------------------------------------------------------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] note: the lint level is defined here [INFO] [stdout] --> src/lib.rs:19:9 [INFO] [stdout] | [INFO] [stdout] 19 | #![deny(warnings)] [INFO] [stdout] | ^^^^^^^^ [INFO] [stdout] = note: `#[deny(mismatched_lifetime_syntaxes)]` implied by `#[deny(warnings)]` [INFO] [stdout] = note: this error originates in the macro `transport_channel_iterator` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] help: one option is to remove the lifetime for references and use the anonymous lifetime for paths [INFO] [stdout] | [INFO] [stdout] 325 | pub fn $func(tr: &mut TransportReceiver) -> $iter<'_> { [INFO] [stdout] | ++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error: lifetime flowing from input to output with different syntax can be confusing [INFO] [stdout] --> src/lib.rs:333:25 [INFO] [stdout] | [INFO] [stdout] 333 | pub fn next(&mut self) -> io::Result<($ty, IpAddr)> { [INFO] [stdout] | ^^^^^^^^^ --- the lifetime gets resolved as `'_` [INFO] [stdout] | | [INFO] [stdout] | this lifetime flows to the output [INFO] [stdout] ... [INFO] [stdout] 444 | transport_channel_iterator!(Ipv4Packet, Ipv4TransportChannelIterator, ipv4_packet_iter); [INFO] [stdout] | --------------------------------------------------------------------------------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: this error originates in the macro `transport_channel_iterator` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] help: one option is to remove the lifetime for references and use the anonymous lifetime for paths [INFO] [stdout] | [INFO] [stdout] 333 | pub fn next(&mut self) -> io::Result<($ty<'_>, IpAddr)> { [INFO] [stdout] | ++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error: lifetime flowing from input to output with different syntax can be confusing [INFO] [stdout] --> src/lib.rs:325:26 [INFO] [stdout] | [INFO] [stdout] 325 | pub fn $func(tr: &mut TransportReceiver) -> $iter { [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^ ----- the lifetime gets resolved as `'_` [INFO] [stdout] | | [INFO] [stdout] | this lifetime flows to the output [INFO] [stdout] ... [INFO] [stdout] 444 | transport_channel_iterator!(Ipv4Packet, Ipv4TransportChannelIterator, ipv4_packet_iter); [INFO] [stdout] | --------------------------------------------------------------------------------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] note: the lint level is defined here [INFO] [stdout] --> src/lib.rs:19:9 [INFO] [stdout] | [INFO] [stdout] 19 | #![deny(warnings)] [INFO] [stdout] | ^^^^^^^^ [INFO] [stdout] = note: `#[deny(mismatched_lifetime_syntaxes)]` implied by `#[deny(warnings)]` [INFO] [stdout] = note: this error originates in the macro `transport_channel_iterator` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] help: one option is to remove the lifetime for references and use the anonymous lifetime for paths [INFO] [stdout] | [INFO] [stdout] 325 | pub fn $func(tr: &mut TransportReceiver) -> $iter<'_> { [INFO] [stdout] | ++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error: lifetime flowing from input to output with different syntax can be confusing [INFO] [stdout] --> src/lib.rs:404:38 [INFO] [stdout] | [INFO] [stdout] 404 | pub fn next_with_timeout(&mut self, t: Duration) -> io::Result> { [INFO] [stdout] | ^^^^^^^^^ this lifetime flows to the output --- the lifetime gets resolved as `'_` [INFO] [stdout] ... [INFO] [stdout] 444 | transport_channel_iterator!(Ipv4Packet, Ipv4TransportChannelIterator, ipv4_packet_iter); [INFO] [stdout] | --------------------------------------------------------------------------------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: this error originates in the macro `transport_channel_iterator` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] help: one option is to remove the lifetime for references and use the anonymous lifetime for paths [INFO] [stdout] | [INFO] [stdout] 404 | pub fn next_with_timeout(&mut self, t: Duration) -> io::Result, IpAddr)>> { [INFO] [stdout] | ++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error: lifetime flowing from input to output with different syntax can be confusing [INFO] [stdout] --> src/lib.rs:333:25 [INFO] [stdout] | [INFO] [stdout] 333 | pub fn next(&mut self) -> io::Result<($ty, IpAddr)> { [INFO] [stdout] | ^^^^^^^^^ --- the lifetime gets resolved as `'_` [INFO] [stdout] | | [INFO] [stdout] | this lifetime flows to the output [INFO] [stdout] ... [INFO] [stdout] 444 | transport_channel_iterator!(Ipv4Packet, Ipv4TransportChannelIterator, ipv4_packet_iter); [INFO] [stdout] | --------------------------------------------------------------------------------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: this error originates in the macro `transport_channel_iterator` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] help: one option is to remove the lifetime for references and use the anonymous lifetime for paths [INFO] [stdout] | [INFO] [stdout] 333 | pub fn next(&mut self) -> io::Result<($ty<'_>, IpAddr)> { [INFO] [stdout] | ++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error: lifetime flowing from input to output with different syntax can be confusing [INFO] [stdout] --> src/lib.rs:325:26 [INFO] [stdout] | [INFO] [stdout] 325 | pub fn $func(tr: &mut TransportReceiver) -> $iter { [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^ ----- the lifetime gets resolved as `'_` [INFO] [stdout] | | [INFO] [stdout] | this lifetime flows to the output [INFO] [stdout] ... [INFO] [stdout] 446 | transport_channel_iterator!(UdpPacket, UdpTransportChannelIterator, udp_packet_iter); [INFO] [stdout] | ------------------------------------------------------------------------------------ in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: this error originates in the macro `transport_channel_iterator` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] help: one option is to remove the lifetime for references and use the anonymous lifetime for paths [INFO] [stdout] | [INFO] [stdout] 325 | pub fn $func(tr: &mut TransportReceiver) -> $iter<'_> { [INFO] [stdout] | ++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error: lifetime flowing from input to output with different syntax can be confusing [INFO] [stdout] --> src/lib.rs:333:25 [INFO] [stdout] | [INFO] [stdout] 333 | pub fn next(&mut self) -> io::Result<($ty, IpAddr)> { [INFO] [stdout] | ^^^^^^^^^ --- the lifetime gets resolved as `'_` [INFO] [stdout] | | [INFO] [stdout] | this lifetime flows to the output [INFO] [stdout] ... [INFO] [stdout] 446 | transport_channel_iterator!(UdpPacket, UdpTransportChannelIterator, udp_packet_iter); [INFO] [stdout] | ------------------------------------------------------------------------------------ in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: this error originates in the macro `transport_channel_iterator` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] help: one option is to remove the lifetime for references and use the anonymous lifetime for paths [INFO] [stdout] | [INFO] [stdout] 333 | pub fn next(&mut self) -> io::Result<($ty<'_>, IpAddr)> { [INFO] [stdout] | ++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error: lifetime flowing from input to output with different syntax can be confusing [INFO] [stdout] --> src/lib.rs:404:38 [INFO] [stdout] | [INFO] [stdout] 404 | pub fn next_with_timeout(&mut self, t: Duration) -> io::Result> { [INFO] [stdout] | ^^^^^^^^^ this lifetime flows to the output --- the lifetime gets resolved as `'_` [INFO] [stdout] ... [INFO] [stdout] 446 | transport_channel_iterator!(UdpPacket, UdpTransportChannelIterator, udp_packet_iter); [INFO] [stdout] | ------------------------------------------------------------------------------------ in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: this error originates in the macro `transport_channel_iterator` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] help: one option is to remove the lifetime for references and use the anonymous lifetime for paths [INFO] [stdout] | [INFO] [stdout] 404 | pub fn next_with_timeout(&mut self, t: Duration) -> io::Result, IpAddr)>> { [INFO] [stdout] | ++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error: lifetime flowing from input to output with different syntax can be confusing [INFO] [stdout] --> src/lib.rs:325:26 [INFO] [stdout] | [INFO] [stdout] 325 | pub fn $func(tr: &mut TransportReceiver) -> $iter { [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^ ----- the lifetime gets resolved as `'_` [INFO] [stdout] | | [INFO] [stdout] | this lifetime flows to the output [INFO] [stdout] ... [INFO] [stdout] 448 | transport_channel_iterator!(IcmpPacket, IcmpTransportChannelIterator, icmp_packet_iter); [INFO] [stdout] | --------------------------------------------------------------------------------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: this error originates in the macro `transport_channel_iterator` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] help: one option is to remove the lifetime for references and use the anonymous lifetime for paths [INFO] [stdout] | [INFO] [stdout] 325 | pub fn $func(tr: &mut TransportReceiver) -> $iter<'_> { [INFO] [stdout] | ++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error: lifetime flowing from input to output with different syntax can be confusing [INFO] [stdout] --> src/lib.rs:404:38 [INFO] [stdout] | [INFO] [stdout] 404 | pub fn next_with_timeout(&mut self, t: Duration) -> io::Result> { [INFO] [stdout] | ^^^^^^^^^ this lifetime flows to the output --- the lifetime gets resolved as `'_` [INFO] [stdout] ... [INFO] [stdout] 444 | transport_channel_iterator!(Ipv4Packet, Ipv4TransportChannelIterator, ipv4_packet_iter); [INFO] [stdout] | --------------------------------------------------------------------------------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: this error originates in the macro `transport_channel_iterator` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] help: one option is to remove the lifetime for references and use the anonymous lifetime for paths [INFO] [stdout] | [INFO] [stdout] 404 | pub fn next_with_timeout(&mut self, t: Duration) -> io::Result, IpAddr)>> { [INFO] [stdout] | ++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error: lifetime flowing from input to output with different syntax can be confusing [INFO] [stdout] --> src/lib.rs:333:25 [INFO] [stdout] | [INFO] [stdout] 333 | pub fn next(&mut self) -> io::Result<($ty, IpAddr)> { [INFO] [stdout] | ^^^^^^^^^ --- the lifetime gets resolved as `'_` [INFO] [stdout] | | [INFO] [stdout] | this lifetime flows to the output [INFO] [stdout] ... [INFO] [stdout] 448 | transport_channel_iterator!(IcmpPacket, IcmpTransportChannelIterator, icmp_packet_iter); [INFO] [stdout] | --------------------------------------------------------------------------------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: this error originates in the macro `transport_channel_iterator` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] help: one option is to remove the lifetime for references and use the anonymous lifetime for paths [INFO] [stdout] | [INFO] [stdout] 333 | pub fn next(&mut self) -> io::Result<($ty<'_>, IpAddr)> { [INFO] [stdout] | ++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error: lifetime flowing from input to output with different syntax can be confusing [INFO] [stdout] --> src/lib.rs:325:26 [INFO] [stdout] | [INFO] [stdout] 325 | pub fn $func(tr: &mut TransportReceiver) -> $iter { [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^ ----- the lifetime gets resolved as `'_` [INFO] [stdout] | | [INFO] [stdout] | this lifetime flows to the output [INFO] [stdout] ... [INFO] [stdout] 446 | transport_channel_iterator!(UdpPacket, UdpTransportChannelIterator, udp_packet_iter); [INFO] [stdout] | ------------------------------------------------------------------------------------ in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: this error originates in the macro `transport_channel_iterator` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] help: one option is to remove the lifetime for references and use the anonymous lifetime for paths [INFO] [stdout] | [INFO] [stdout] 325 | pub fn $func(tr: &mut TransportReceiver) -> $iter<'_> { [INFO] [stdout] | ++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error: lifetime flowing from input to output with different syntax can be confusing [INFO] [stdout] --> src/lib.rs:333:25 [INFO] [stdout] | [INFO] [stdout] 333 | pub fn next(&mut self) -> io::Result<($ty, IpAddr)> { [INFO] [stdout] | ^^^^^^^^^ --- the lifetime gets resolved as `'_` [INFO] [stdout] | | [INFO] [stdout] | this lifetime flows to the output [INFO] [stdout] ... [INFO] [stdout] 446 | transport_channel_iterator!(UdpPacket, UdpTransportChannelIterator, udp_packet_iter); [INFO] [stdout] | ------------------------------------------------------------------------------------ in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: this error originates in the macro `transport_channel_iterator` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] help: one option is to remove the lifetime for references and use the anonymous lifetime for paths [INFO] [stdout] | [INFO] [stdout] 333 | pub fn next(&mut self) -> io::Result<($ty<'_>, IpAddr)> { [INFO] [stdout] | ++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error: lifetime flowing from input to output with different syntax can be confusing [INFO] [stdout] --> src/lib.rs:404:38 [INFO] [stdout] | [INFO] [stdout] 404 | pub fn next_with_timeout(&mut self, t: Duration) -> io::Result> { [INFO] [stdout] | ^^^^^^^^^ this lifetime flows to the output --- the lifetime gets resolved as `'_` [INFO] [stdout] ... [INFO] [stdout] 446 | transport_channel_iterator!(UdpPacket, UdpTransportChannelIterator, udp_packet_iter); [INFO] [stdout] | ------------------------------------------------------------------------------------ in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: this error originates in the macro `transport_channel_iterator` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] help: one option is to remove the lifetime for references and use the anonymous lifetime for paths [INFO] [stdout] | [INFO] [stdout] 404 | pub fn next_with_timeout(&mut self, t: Duration) -> io::Result, IpAddr)>> { [INFO] [stdout] | ++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error: lifetime flowing from input to output with different syntax can be confusing [INFO] [stdout] --> src/lib.rs:325:26 [INFO] [stdout] | [INFO] [stdout] 325 | pub fn $func(tr: &mut TransportReceiver) -> $iter { [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^ ----- the lifetime gets resolved as `'_` [INFO] [stdout] | | [INFO] [stdout] | this lifetime flows to the output [INFO] [stdout] ... [INFO] [stdout] 448 | transport_channel_iterator!(IcmpPacket, IcmpTransportChannelIterator, icmp_packet_iter); [INFO] [stdout] | --------------------------------------------------------------------------------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: this error originates in the macro `transport_channel_iterator` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] help: one option is to remove the lifetime for references and use the anonymous lifetime for paths [INFO] [stdout] | [INFO] [stdout] 325 | pub fn $func(tr: &mut TransportReceiver) -> $iter<'_> { [INFO] [stdout] | ++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error: lifetime flowing from input to output with different syntax can be confusing [INFO] [stdout] --> src/lib.rs:333:25 [INFO] [stdout] | [INFO] [stdout] 333 | pub fn next(&mut self) -> io::Result<($ty, IpAddr)> { [INFO] [stdout] | ^^^^^^^^^ --- the lifetime gets resolved as `'_` [INFO] [stdout] | | [INFO] [stdout] | this lifetime flows to the output [INFO] [stdout] ... [INFO] [stdout] 448 | transport_channel_iterator!(IcmpPacket, IcmpTransportChannelIterator, icmp_packet_iter); [INFO] [stdout] | --------------------------------------------------------------------------------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: this error originates in the macro `transport_channel_iterator` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] help: one option is to remove the lifetime for references and use the anonymous lifetime for paths [INFO] [stdout] | [INFO] [stdout] 333 | pub fn next(&mut self) -> io::Result<($ty<'_>, IpAddr)> { [INFO] [stdout] | ++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error: lifetime flowing from input to output with different syntax can be confusing [INFO] [stdout] --> src/lib.rs:404:38 [INFO] [stdout] | [INFO] [stdout] 404 | pub fn next_with_timeout(&mut self, t: Duration) -> io::Result> { [INFO] [stdout] | ^^^^^^^^^ this lifetime flows to the output --- the lifetime gets resolved as `'_` [INFO] [stdout] ... [INFO] [stdout] 448 | transport_channel_iterator!(IcmpPacket, IcmpTransportChannelIterator, icmp_packet_iter); [INFO] [stdout] | --------------------------------------------------------------------------------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: this error originates in the macro `transport_channel_iterator` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] help: one option is to remove the lifetime for references and use the anonymous lifetime for paths [INFO] [stdout] | [INFO] [stdout] 404 | pub fn next_with_timeout(&mut self, t: Duration) -> io::Result, IpAddr)>> { [INFO] [stdout] | ++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error: lifetime flowing from input to output with different syntax can be confusing [INFO] [stdout] --> src/lib.rs:325:26 [INFO] [stdout] | [INFO] [stdout] 325 | pub fn $func(tr: &mut TransportReceiver) -> $iter { [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^ ----- the lifetime gets resolved as `'_` [INFO] [stdout] | | [INFO] [stdout] | this lifetime flows to the output [INFO] [stdout] ... [INFO] [stdout] 450 | / transport_channel_iterator!( [INFO] [stdout] 451 | | Icmpv6Packet, [INFO] [stdout] 452 | | Icmpv6TransportChannelIterator, [INFO] [stdout] 453 | | icmpv6_packet_iter [INFO] [stdout] 454 | | ); [INFO] [stdout] | |_- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: this error originates in the macro `transport_channel_iterator` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] help: one option is to remove the lifetime for references and use the anonymous lifetime for paths [INFO] [stdout] | [INFO] [stdout] 325 | pub fn $func(tr: &mut TransportReceiver) -> $iter<'_> { [INFO] [stdout] | ++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error: lifetime flowing from input to output with different syntax can be confusing [INFO] [stdout] --> src/lib.rs:333:25 [INFO] [stdout] | [INFO] [stdout] 333 | pub fn next(&mut self) -> io::Result<($ty, IpAddr)> { [INFO] [stdout] | ^^^^^^^^^ --- the lifetime gets resolved as `'_` [INFO] [stdout] | | [INFO] [stdout] | this lifetime flows to the output [INFO] [stdout] ... [INFO] [stdout] 450 | / transport_channel_iterator!( [INFO] [stdout] 451 | | Icmpv6Packet, [INFO] [stdout] 452 | | Icmpv6TransportChannelIterator, [INFO] [stdout] 453 | | icmpv6_packet_iter [INFO] [stdout] 454 | | ); [INFO] [stdout] | |_- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: this error originates in the macro `transport_channel_iterator` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] help: one option is to remove the lifetime for references and use the anonymous lifetime for paths [INFO] [stdout] | [INFO] [stdout] 333 | pub fn next(&mut self) -> io::Result<($ty<'_>, IpAddr)> { [INFO] [stdout] | ++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error: lifetime flowing from input to output with different syntax can be confusing [INFO] [stdout] --> src/lib.rs:404:38 [INFO] [stdout] | [INFO] [stdout] 404 | pub fn next_with_timeout(&mut self, t: Duration) -> io::Result> { [INFO] [stdout] | ^^^^^^^^^ this lifetime flows to the output --- the lifetime gets resolved as `'_` [INFO] [stdout] ... [INFO] [stdout] 450 | / transport_channel_iterator!( [INFO] [stdout] 451 | | Icmpv6Packet, [INFO] [stdout] 452 | | Icmpv6TransportChannelIterator, [INFO] [stdout] 453 | | icmpv6_packet_iter [INFO] [stdout] 454 | | ); [INFO] [stdout] | |_- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: this error originates in the macro `transport_channel_iterator` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] help: one option is to remove the lifetime for references and use the anonymous lifetime for paths [INFO] [stdout] | [INFO] [stdout] 404 | pub fn next_with_timeout(&mut self, t: Duration) -> io::Result, IpAddr)>> { [INFO] [stdout] | ++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error: lifetime flowing from input to output with different syntax can be confusing [INFO] [stdout] --> src/lib.rs:325:26 [INFO] [stdout] | [INFO] [stdout] 325 | pub fn $func(tr: &mut TransportReceiver) -> $iter { [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^ ----- the lifetime gets resolved as `'_` [INFO] [stdout] | | [INFO] [stdout] | this lifetime flows to the output [INFO] [stdout] ... [INFO] [stdout] 456 | transport_channel_iterator!(TcpPacket, TcpTransportChannelIterator, tcp_packet_iter); [INFO] [stdout] | ------------------------------------------------------------------------------------ in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: this error originates in the macro `transport_channel_iterator` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] help: one option is to remove the lifetime for references and use the anonymous lifetime for paths [INFO] [stdout] | [INFO] [stdout] 325 | pub fn $func(tr: &mut TransportReceiver) -> $iter<'_> { [INFO] [stdout] | ++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error: lifetime flowing from input to output with different syntax can be confusing [INFO] [stdout] --> src/lib.rs:333:25 [INFO] [stdout] | [INFO] [stdout] 333 | pub fn next(&mut self) -> io::Result<($ty, IpAddr)> { [INFO] [stdout] | ^^^^^^^^^ --- the lifetime gets resolved as `'_` [INFO] [stdout] | | [INFO] [stdout] | this lifetime flows to the output [INFO] [stdout] ... [INFO] [stdout] 456 | transport_channel_iterator!(TcpPacket, TcpTransportChannelIterator, tcp_packet_iter); [INFO] [stdout] | ------------------------------------------------------------------------------------ in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: this error originates in the macro `transport_channel_iterator` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] help: one option is to remove the lifetime for references and use the anonymous lifetime for paths [INFO] [stdout] | [INFO] [stdout] 333 | pub fn next(&mut self) -> io::Result<($ty<'_>, IpAddr)> { [INFO] [stdout] | ++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error: lifetime flowing from input to output with different syntax can be confusing [INFO] [stdout] --> src/lib.rs:404:38 [INFO] [stdout] | [INFO] [stdout] 404 | pub fn next_with_timeout(&mut self, t: Duration) -> io::Result> { [INFO] [stdout] | ^^^^^^^^^ this lifetime flows to the output --- the lifetime gets resolved as `'_` [INFO] [stdout] ... [INFO] [stdout] 456 | transport_channel_iterator!(TcpPacket, TcpTransportChannelIterator, tcp_packet_iter); [INFO] [stdout] | ------------------------------------------------------------------------------------ in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: this error originates in the macro `transport_channel_iterator` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] help: one option is to remove the lifetime for references and use the anonymous lifetime for paths [INFO] [stdout] | [INFO] [stdout] 404 | pub fn next_with_timeout(&mut self, t: Duration) -> io::Result, IpAddr)>> { [INFO] [stdout] | ++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error: lifetime flowing from input to output with different syntax can be confusing [INFO] [stdout] --> src/lib.rs:404:38 [INFO] [stdout] | [INFO] [stdout] 404 | pub fn next_with_timeout(&mut self, t: Duration) -> io::Result> { [INFO] [stdout] | ^^^^^^^^^ this lifetime flows to the output --- the lifetime gets resolved as `'_` [INFO] [stdout] ... [INFO] [stdout] 448 | transport_channel_iterator!(IcmpPacket, IcmpTransportChannelIterator, icmp_packet_iter); [INFO] [stdout] | --------------------------------------------------------------------------------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: this error originates in the macro `transport_channel_iterator` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] help: one option is to remove the lifetime for references and use the anonymous lifetime for paths [INFO] [stdout] | [INFO] [stdout] 404 | pub fn next_with_timeout(&mut self, t: Duration) -> io::Result, IpAddr)>> { [INFO] [stdout] | ++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error: lifetime flowing from input to output with different syntax can be confusing [INFO] [stdout] --> src/lib.rs:325:26 [INFO] [stdout] | [INFO] [stdout] 325 | pub fn $func(tr: &mut TransportReceiver) -> $iter { [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^ ----- the lifetime gets resolved as `'_` [INFO] [stdout] | | [INFO] [stdout] | this lifetime flows to the output [INFO] [stdout] ... [INFO] [stdout] 450 | / transport_channel_iterator!( [INFO] [stdout] 451 | | Icmpv6Packet, [INFO] [stdout] 452 | | Icmpv6TransportChannelIterator, [INFO] [stdout] 453 | | icmpv6_packet_iter [INFO] [stdout] 454 | | ); [INFO] [stdout] | |_- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: this error originates in the macro `transport_channel_iterator` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] help: one option is to remove the lifetime for references and use the anonymous lifetime for paths [INFO] [stdout] | [INFO] [stdout] 325 | pub fn $func(tr: &mut TransportReceiver) -> $iter<'_> { [INFO] [stdout] | ++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error: lifetime flowing from input to output with different syntax can be confusing [INFO] [stdout] --> src/lib.rs:333:25 [INFO] [stdout] | [INFO] [stdout] 333 | pub fn next(&mut self) -> io::Result<($ty, IpAddr)> { [INFO] [stdout] | ^^^^^^^^^ --- the lifetime gets resolved as `'_` [INFO] [stdout] | | [INFO] [stdout] | this lifetime flows to the output [INFO] [stdout] ... [INFO] [stdout] 450 | / transport_channel_iterator!( [INFO] [stdout] 451 | | Icmpv6Packet, [INFO] [stdout] 452 | | Icmpv6TransportChannelIterator, [INFO] [stdout] 453 | | icmpv6_packet_iter [INFO] [stdout] 454 | | ); [INFO] [stdout] | |_- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: this error originates in the macro `transport_channel_iterator` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] help: one option is to remove the lifetime for references and use the anonymous lifetime for paths [INFO] [stdout] | [INFO] [stdout] 333 | pub fn next(&mut self) -> io::Result<($ty<'_>, IpAddr)> { [INFO] [stdout] | ++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stderr] error: could not compile `pnet_transport` (lib) due to 15 previous errors [INFO] [stderr] warning: build failed, waiting for other jobs to finish... [INFO] [stdout] error: lifetime flowing from input to output with different syntax can be confusing [INFO] [stdout] --> src/lib.rs:404:38 [INFO] [stdout] | [INFO] [stdout] 404 | pub fn next_with_timeout(&mut self, t: Duration) -> io::Result> { [INFO] [stdout] | ^^^^^^^^^ this lifetime flows to the output --- the lifetime gets resolved as `'_` [INFO] [stdout] ... [INFO] [stdout] 450 | / transport_channel_iterator!( [INFO] [stdout] 451 | | Icmpv6Packet, [INFO] [stdout] 452 | | Icmpv6TransportChannelIterator, [INFO] [stdout] 453 | | icmpv6_packet_iter [INFO] [stdout] 454 | | ); [INFO] [stdout] | |_- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: this error originates in the macro `transport_channel_iterator` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] help: one option is to remove the lifetime for references and use the anonymous lifetime for paths [INFO] [stdout] | [INFO] [stdout] 404 | pub fn next_with_timeout(&mut self, t: Duration) -> io::Result, IpAddr)>> { [INFO] [stdout] | ++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error: lifetime flowing from input to output with different syntax can be confusing [INFO] [stdout] --> src/lib.rs:325:26 [INFO] [stdout] | [INFO] [stdout] 325 | pub fn $func(tr: &mut TransportReceiver) -> $iter { [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^ ----- the lifetime gets resolved as `'_` [INFO] [stdout] | | [INFO] [stdout] | this lifetime flows to the output [INFO] [stdout] ... [INFO] [stdout] 456 | transport_channel_iterator!(TcpPacket, TcpTransportChannelIterator, tcp_packet_iter); [INFO] [stdout] | ------------------------------------------------------------------------------------ in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: this error originates in the macro `transport_channel_iterator` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] help: one option is to remove the lifetime for references and use the anonymous lifetime for paths [INFO] [stdout] | [INFO] [stdout] 325 | pub fn $func(tr: &mut TransportReceiver) -> $iter<'_> { [INFO] [stdout] | ++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error: lifetime flowing from input to output with different syntax can be confusing [INFO] [stdout] --> src/lib.rs:333:25 [INFO] [stdout] | [INFO] [stdout] 333 | pub fn next(&mut self) -> io::Result<($ty, IpAddr)> { [INFO] [stdout] | ^^^^^^^^^ --- the lifetime gets resolved as `'_` [INFO] [stdout] | | [INFO] [stdout] | this lifetime flows to the output [INFO] [stdout] ... [INFO] [stdout] 456 | transport_channel_iterator!(TcpPacket, TcpTransportChannelIterator, tcp_packet_iter); [INFO] [stdout] | ------------------------------------------------------------------------------------ in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: this error originates in the macro `transport_channel_iterator` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] help: one option is to remove the lifetime for references and use the anonymous lifetime for paths [INFO] [stdout] | [INFO] [stdout] 333 | pub fn next(&mut self) -> io::Result<($ty<'_>, IpAddr)> { [INFO] [stdout] | ++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error: lifetime flowing from input to output with different syntax can be confusing [INFO] [stdout] --> src/lib.rs:404:38 [INFO] [stdout] | [INFO] [stdout] 404 | pub fn next_with_timeout(&mut self, t: Duration) -> io::Result> { [INFO] [stdout] | ^^^^^^^^^ this lifetime flows to the output --- the lifetime gets resolved as `'_` [INFO] [stdout] ... [INFO] [stdout] 456 | transport_channel_iterator!(TcpPacket, TcpTransportChannelIterator, tcp_packet_iter); [INFO] [stdout] | ------------------------------------------------------------------------------------ in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: this error originates in the macro `transport_channel_iterator` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] help: one option is to remove the lifetime for references and use the anonymous lifetime for paths [INFO] [stdout] | [INFO] [stdout] 404 | pub fn next_with_timeout(&mut self, t: Duration) -> io::Result, IpAddr)>> { [INFO] [stdout] | ++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stderr] error: could not compile `pnet_transport` (lib test) due to 15 previous errors [INFO] running `Command { std: "docker" "inspect" "f2ade8c87b5a9de226125100c516c8b0c4b39140cde2b06161c22aef934e2428", kill_on_drop: false }` [INFO] running `Command { std: "docker" "rm" "-f" "f2ade8c87b5a9de226125100c516c8b0c4b39140cde2b06161c22aef934e2428", kill_on_drop: false }` [INFO] [stdout] f2ade8c87b5a9de226125100c516c8b0c4b39140cde2b06161c22aef934e2428