[INFO] fetching crate laminar 0.4.0... [INFO] testing laminar-0.4.0 against 1.49.0 for beta-1.50-1 [INFO] extracting crate laminar 0.4.0 into /workspace/builds/worker-12/source [INFO] validating manifest of crates.io crate laminar 0.4.0 on toolchain 1.49.0 [INFO] running `Command { std: "/workspace/cargo-home/bin/cargo" "+1.49.0" "read-manifest" "--manifest-path" "Cargo.toml", kill_on_drop: false }` [INFO] started tweaking crates.io crate laminar 0.4.0 [INFO] finished tweaking crates.io crate laminar 0.4.0 [INFO] tweaked toml for crates.io crate laminar 0.4.0 written to /workspace/builds/worker-12/source/Cargo.toml [INFO] crate crates.io crate laminar 0.4.0 already has a lockfile, it will not be regenerated [INFO] running `Command { std: "/workspace/cargo-home/bin/cargo" "+1.49.0" "fetch" "--locked" "--manifest-path" "Cargo.toml", kill_on_drop: false }` [INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-12/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-12/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" "rustops/crates-build-env@sha256:b8eeb62f26c39b23691079a6cb6de528d8e88b4d71a8f6b1d30f8ba7d9c16de9" "/opt/rustwide/cargo-home/bin/cargo" "+1.49.0" "metadata" "--no-deps" "--format-version=1", kill_on_drop: false }` [INFO] [stdout] fe1ffcf5f9e1007f12419fc76bfbfc402d2ebcdd82f4a7a334afba339c2911c1 [INFO] [stderr] WARNING: Your kernel does not support swap limit capabilities or the cgroup is not mounted. Memory limited without swap. [INFO] running `Command { std: "docker" "start" "-a" "fe1ffcf5f9e1007f12419fc76bfbfc402d2ebcdd82f4a7a334afba339c2911c1", kill_on_drop: false }` [INFO] running `Command { std: "docker" "inspect" "fe1ffcf5f9e1007f12419fc76bfbfc402d2ebcdd82f4a7a334afba339c2911c1", kill_on_drop: false }` [INFO] running `Command { std: "docker" "rm" "-f" "fe1ffcf5f9e1007f12419fc76bfbfc402d2ebcdd82f4a7a334afba339c2911c1", kill_on_drop: false }` [INFO] [stdout] fe1ffcf5f9e1007f12419fc76bfbfc402d2ebcdd82f4a7a334afba339c2911c1 [INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-12/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-12/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=warn" "-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" "rustops/crates-build-env@sha256:b8eeb62f26c39b23691079a6cb6de528d8e88b4d71a8f6b1d30f8ba7d9c16de9" "/opt/rustwide/cargo-home/bin/cargo" "+1.49.0" "build" "--frozen" "--message-format=json", kill_on_drop: false }` [INFO] [stdout] 8fb71b06ab935835176cdcac2ad52276cb5626520805444b4ffb72cd956b8f77 [INFO] [stderr] WARNING: Your kernel does not support swap limit capabilities or the cgroup is not mounted. Memory limited without swap. [INFO] running `Command { std: "docker" "start" "-a" "8fb71b06ab935835176cdcac2ad52276cb5626520805444b4ffb72cd956b8f77", kill_on_drop: false }` [INFO] [stderr] Compiling getrandom v0.1.12 [INFO] [stderr] Compiling c2-chacha v0.2.2 [INFO] [stderr] Compiling log v0.4.8 [INFO] [stderr] Compiling crossbeam-utils v0.7.2 [INFO] [stderr] Compiling crossbeam-channel v0.4.4 [INFO] [stderr] Compiling rand_core v0.5.1 [INFO] [stderr] Compiling rand_chacha v0.2.1 [INFO] [stderr] Compiling rand_pcg v0.2.0 [INFO] [stderr] Compiling rand v0.7.0 [INFO] [stderr] Compiling laminar v0.4.0 (/opt/rustwide/workdir) [INFO] [stderr] Finished dev [unoptimized + debuginfo] target(s) in 11.34s [INFO] running `Command { std: "docker" "inspect" "8fb71b06ab935835176cdcac2ad52276cb5626520805444b4ffb72cd956b8f77", kill_on_drop: false }` [INFO] running `Command { std: "docker" "rm" "-f" "8fb71b06ab935835176cdcac2ad52276cb5626520805444b4ffb72cd956b8f77", kill_on_drop: false }` [INFO] [stdout] 8fb71b06ab935835176cdcac2ad52276cb5626520805444b4ffb72cd956b8f77 [INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-12/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-12/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=warn" "-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" "rustops/crates-build-env@sha256:b8eeb62f26c39b23691079a6cb6de528d8e88b4d71a8f6b1d30f8ba7d9c16de9" "/opt/rustwide/cargo-home/bin/cargo" "+1.49.0" "test" "--frozen" "--no-run" "--message-format=json", kill_on_drop: false }` [INFO] [stdout] c6654b5547576d29a35a26024d518b9befca8b1ebd76a741a096687a46bb0e23 [INFO] [stderr] WARNING: Your kernel does not support swap limit capabilities or the cgroup is not mounted. Memory limited without swap. [INFO] running `Command { std: "docker" "start" "-a" "c6654b5547576d29a35a26024d518b9befca8b1ebd76a741a096687a46bb0e23", kill_on_drop: false }` [INFO] [stderr] Compiling proc-macro2 v1.0.2 [INFO] [stderr] Compiling regex-syntax v0.6.12 [INFO] [stderr] Compiling bincode v1.3.1 [INFO] [stderr] Compiling quickcheck_macros v0.8.0 [INFO] [stderr] Compiling quote v1.0.2 [INFO] [stderr] Compiling syn v1.0.5 [INFO] [stderr] Compiling regex v1.3.1 [INFO] [stderr] Compiling env_logger v0.6.2 [INFO] [stderr] Compiling quickcheck v0.9.0 [INFO] [stderr] Compiling serde_derive v1.0.99 [INFO] [stderr] Compiling laminar v0.4.0 (/opt/rustwide/workdir) [INFO] [stdout] warning: unused variable: `client_addr` [INFO] [stdout] --> tests/basic_socket_test.rs:38:9 [INFO] [stdout] | [INFO] [stdout] 38 | let client_addr = client.local_addr().unwrap(); [INFO] [stdout] | ^^^^^^^^^^^ help: if this is intentional, prefix it with an underscore: `_client_addr` [INFO] [stdout] | [INFO] [stdout] = note: `#[warn(unused_variables)]` on by default [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unused import: `Ipv4Addr` [INFO] [stdout] --> src/net/connection_manager.rs:212:15 [INFO] [stdout] | [INFO] [stdout] 212 | net::{Ipv4Addr, SocketAddr, SocketAddrV4}, [INFO] [stdout] | ^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: `#[warn(unused_imports)]` on by default [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: 1 warning emitted [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: this method call currently resolves to `<&[T; N] as IntoIterator>::into_iter` (due to autoref coercions), but that might change in the future when `IntoIterator` impls for arrays are added. [INFO] [stdout] --> src/infrastructure/arranging/ordering.rs:447:51 [INFO] [stdout] | [INFO] [stdout] 447 | let ordered_packets : Vec<_> = before.into_iter() [INFO] [stdout] | ^^^^^^^^^ help: use `.iter()` instead of `.into_iter()` to avoid ambiguity: `iter` [INFO] [stdout] ... [INFO] [stdout] 465 | assert_order!([0, 2, 4, 3, 1], [0, 1, 2, 3, 4], 1); [INFO] [stdout] | --------------------------------------------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: `#[warn(array_into_iter)]` on by default [INFO] [stdout] = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in a future release! [INFO] [stdout] = note: for more information, see issue #66145 [INFO] [stdout] = note: this warning originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: this method call currently resolves to `<&[T; N] as IntoIterator>::into_iter` (due to autoref coercions), but that might change in the future when `IntoIterator` impls for arrays are added. [INFO] [stdout] --> src/infrastructure/arranging/ordering.rs:447:51 [INFO] [stdout] | [INFO] [stdout] 447 | let ordered_packets : Vec<_> = before.into_iter() [INFO] [stdout] | ^^^^^^^^^ help: use `.iter()` instead of `.into_iter()` to avoid ambiguity: `iter` [INFO] [stdout] ... [INFO] [stdout] 466 | assert_order!([0, 4, 3, 2, 1], [0, 1, 2, 3, 4], 1); [INFO] [stdout] | --------------------------------------------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in a future release! [INFO] [stdout] = note: for more information, see issue #66145 [INFO] [stdout] = note: this warning originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: this method call currently resolves to `<&[T; N] as IntoIterator>::into_iter` (due to autoref coercions), but that might change in the future when `IntoIterator` impls for arrays are added. [INFO] [stdout] --> src/infrastructure/arranging/ordering.rs:447:51 [INFO] [stdout] | [INFO] [stdout] 447 | let ordered_packets : Vec<_> = before.into_iter() [INFO] [stdout] | ^^^^^^^^^ help: use `.iter()` instead of `.into_iter()` to avoid ambiguity: `iter` [INFO] [stdout] ... [INFO] [stdout] 467 | assert_order!([4, 2, 3, 1, 0], [0, 1, 2, 3, 4], 1); [INFO] [stdout] | --------------------------------------------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in a future release! [INFO] [stdout] = note: for more information, see issue #66145 [INFO] [stdout] = note: this warning originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: this method call currently resolves to `<&[T; N] as IntoIterator>::into_iter` (due to autoref coercions), but that might change in the future when `IntoIterator` impls for arrays are added. [INFO] [stdout] --> src/infrastructure/arranging/ordering.rs:447:51 [INFO] [stdout] | [INFO] [stdout] 447 | let ordered_packets : Vec<_> = before.into_iter() [INFO] [stdout] | ^^^^^^^^^ help: use `.iter()` instead of `.into_iter()` to avoid ambiguity: `iter` [INFO] [stdout] ... [INFO] [stdout] 468 | assert_order!([3, 2, 1, 0, 4], [0, 1, 2, 3, 4], 1); [INFO] [stdout] | --------------------------------------------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in a future release! [INFO] [stdout] = note: for more information, see issue #66145 [INFO] [stdout] = note: this warning originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: this method call currently resolves to `<&[T; N] as IntoIterator>::into_iter` (due to autoref coercions), but that might change in the future when `IntoIterator` impls for arrays are added. [INFO] [stdout] --> src/infrastructure/arranging/ordering.rs:447:51 [INFO] [stdout] | [INFO] [stdout] 447 | let ordered_packets : Vec<_> = before.into_iter() [INFO] [stdout] | ^^^^^^^^^ help: use `.iter()` instead of `.into_iter()` to avoid ambiguity: `iter` [INFO] [stdout] ... [INFO] [stdout] 469 | assert_order!([1, 0, 3, 2, 4], [0, 1, 2, 3, 4], 1); [INFO] [stdout] | --------------------------------------------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in a future release! [INFO] [stdout] = note: for more information, see issue #66145 [INFO] [stdout] = note: this warning originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: this method call currently resolves to `<&[T; N] as IntoIterator>::into_iter` (due to autoref coercions), but that might change in the future when `IntoIterator` impls for arrays are added. [INFO] [stdout] --> src/infrastructure/arranging/ordering.rs:447:51 [INFO] [stdout] | [INFO] [stdout] 447 | let ordered_packets : Vec<_> = before.into_iter() [INFO] [stdout] | ^^^^^^^^^ help: use `.iter()` instead of `.into_iter()` to avoid ambiguity: `iter` [INFO] [stdout] ... [INFO] [stdout] 470 | assert_order!([4, 1, 0, 3, 2], [0, 1, 2, 3, 4], 1); [INFO] [stdout] | --------------------------------------------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in a future release! [INFO] [stdout] = note: for more information, see issue #66145 [INFO] [stdout] = note: this warning originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: this method call currently resolves to `<&[T; N] as IntoIterator>::into_iter` (due to autoref coercions), but that might change in the future when `IntoIterator` impls for arrays are added. [INFO] [stdout] --> src/infrastructure/arranging/ordering.rs:447:51 [INFO] [stdout] | [INFO] [stdout] 447 | let ordered_packets : Vec<_> = before.into_iter() [INFO] [stdout] | ^^^^^^^^^ help: use `.iter()` instead of `.into_iter()` to avoid ambiguity: `iter` [INFO] [stdout] ... [INFO] [stdout] 471 | assert_order!([2, 1, 3, 0, 4], [0, 1, 2, 3, 4], 1); [INFO] [stdout] | --------------------------------------------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in a future release! [INFO] [stdout] = note: for more information, see issue #66145 [INFO] [stdout] = note: this warning originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: this method call currently resolves to `<&[T; N] as IntoIterator>::into_iter` (due to autoref coercions), but that might change in the future when `IntoIterator` impls for arrays are added. [INFO] [stdout] --> src/infrastructure/arranging/ordering.rs:447:51 [INFO] [stdout] | [INFO] [stdout] 447 | let ordered_packets : Vec<_> = before.into_iter() [INFO] [stdout] | ^^^^^^^^^ help: use `.iter()` instead of `.into_iter()` to avoid ambiguity: `iter` [INFO] [stdout] ... [INFO] [stdout] 472 | assert_order!([1, 0, 3, 2, 4], [0, 1, 2, 3, 4], 1); [INFO] [stdout] | --------------------------------------------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in a future release! [INFO] [stdout] = note: for more information, see issue #66145 [INFO] [stdout] = note: this warning originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: this method call currently resolves to `<&[T; N] as IntoIterator>::into_iter` (due to autoref coercions), but that might change in the future when `IntoIterator` impls for arrays are added. [INFO] [stdout] --> src/infrastructure/arranging/ordering.rs:447:51 [INFO] [stdout] | [INFO] [stdout] 447 | let ordered_packets : Vec<_> = before.into_iter() [INFO] [stdout] | ^^^^^^^^^ help: use `.iter()` instead of `.into_iter()` to avoid ambiguity: `iter` [INFO] [stdout] ... [INFO] [stdout] 478 | assert_order!([0, 2, 4, 3, 1], [0, 1, 2, 3, 4], 1); [INFO] [stdout] | --------------------------------------------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in a future release! [INFO] [stdout] = note: for more information, see issue #66145 [INFO] [stdout] = note: this warning originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: this method call currently resolves to `<&[T; N] as IntoIterator>::into_iter` (due to autoref coercions), but that might change in the future when `IntoIterator` impls for arrays are added. [INFO] [stdout] --> src/infrastructure/arranging/ordering.rs:447:51 [INFO] [stdout] | [INFO] [stdout] 447 | let ordered_packets : Vec<_> = before.into_iter() [INFO] [stdout] | ^^^^^^^^^ help: use `.iter()` instead of `.into_iter()` to avoid ambiguity: `iter` [INFO] [stdout] ... [INFO] [stdout] 479 | assert_order!([0, 4, 3, 2, 1], [0, 1, 2, 3, 4], 2); [INFO] [stdout] | --------------------------------------------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in a future release! [INFO] [stdout] = note: for more information, see issue #66145 [INFO] [stdout] = note: this warning originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: this method call currently resolves to `<&[T; N] as IntoIterator>::into_iter` (due to autoref coercions), but that might change in the future when `IntoIterator` impls for arrays are added. [INFO] [stdout] --> src/infrastructure/arranging/ordering.rs:447:51 [INFO] [stdout] | [INFO] [stdout] 447 | let ordered_packets : Vec<_> = before.into_iter() [INFO] [stdout] | ^^^^^^^^^ help: use `.iter()` instead of `.into_iter()` to avoid ambiguity: `iter` [INFO] [stdout] ... [INFO] [stdout] 480 | assert_order!([4, 2, 3, 1, 0], [0, 1, 2, 3, 4], 3); [INFO] [stdout] | --------------------------------------------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in a future release! [INFO] [stdout] = note: for more information, see issue #66145 [INFO] [stdout] = note: this warning originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: this method call currently resolves to `<&[T; N] as IntoIterator>::into_iter` (due to autoref coercions), but that might change in the future when `IntoIterator` impls for arrays are added. [INFO] [stdout] --> src/infrastructure/arranging/ordering.rs:447:51 [INFO] [stdout] | [INFO] [stdout] 447 | let ordered_packets : Vec<_> = before.into_iter() [INFO] [stdout] | ^^^^^^^^^ help: use `.iter()` instead of `.into_iter()` to avoid ambiguity: `iter` [INFO] [stdout] ... [INFO] [stdout] 481 | assert_order!([3, 2, 1, 0, 4], [0, 1, 2, 3, 4], 4); [INFO] [stdout] | --------------------------------------------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in a future release! [INFO] [stdout] = note: for more information, see issue #66145 [INFO] [stdout] = note: this warning originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: this method call currently resolves to `<&[T; N] as IntoIterator>::into_iter` (due to autoref coercions), but that might change in the future when `IntoIterator` impls for arrays are added. [INFO] [stdout] --> src/infrastructure/arranging/ordering.rs:447:51 [INFO] [stdout] | [INFO] [stdout] 447 | let ordered_packets : Vec<_> = before.into_iter() [INFO] [stdout] | ^^^^^^^^^ help: use `.iter()` instead of `.into_iter()` to avoid ambiguity: `iter` [INFO] [stdout] ... [INFO] [stdout] 482 | assert_order!([1, 0, 3, 2, 4], [0, 1, 2, 3, 4], 5); [INFO] [stdout] | --------------------------------------------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in a future release! [INFO] [stdout] = note: for more information, see issue #66145 [INFO] [stdout] = note: this warning originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: this method call currently resolves to `<&[T; N] as IntoIterator>::into_iter` (due to autoref coercions), but that might change in the future when `IntoIterator` impls for arrays are added. [INFO] [stdout] --> src/infrastructure/arranging/ordering.rs:447:51 [INFO] [stdout] | [INFO] [stdout] 447 | let ordered_packets : Vec<_> = before.into_iter() [INFO] [stdout] | ^^^^^^^^^ help: use `.iter()` instead of `.into_iter()` to avoid ambiguity: `iter` [INFO] [stdout] ... [INFO] [stdout] 483 | assert_order!([4, 1, 0, 3, 2], [0, 1, 2, 3, 4], 6); [INFO] [stdout] | --------------------------------------------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in a future release! [INFO] [stdout] = note: for more information, see issue #66145 [INFO] [stdout] = note: this warning originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: this method call currently resolves to `<&[T; N] as IntoIterator>::into_iter` (due to autoref coercions), but that might change in the future when `IntoIterator` impls for arrays are added. [INFO] [stdout] --> src/infrastructure/arranging/ordering.rs:447:51 [INFO] [stdout] | [INFO] [stdout] 447 | let ordered_packets : Vec<_> = before.into_iter() [INFO] [stdout] | ^^^^^^^^^ help: use `.iter()` instead of `.into_iter()` to avoid ambiguity: `iter` [INFO] [stdout] ... [INFO] [stdout] 484 | assert_order!([2, 1, 3, 0, 4], [0, 1, 2, 3, 4], 7); [INFO] [stdout] | --------------------------------------------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in a future release! [INFO] [stdout] = note: for more information, see issue #66145 [INFO] [stdout] = note: this warning originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: this method call currently resolves to `<&[T; N] as IntoIterator>::into_iter` (due to autoref coercions), but that might change in the future when `IntoIterator` impls for arrays are added. [INFO] [stdout] --> src/infrastructure/arranging/ordering.rs:447:51 [INFO] [stdout] | [INFO] [stdout] 447 | let ordered_packets : Vec<_> = before.into_iter() [INFO] [stdout] | ^^^^^^^^^ help: use `.iter()` instead of `.into_iter()` to avoid ambiguity: `iter` [INFO] [stdout] ... [INFO] [stdout] 485 | assert_order!([1, 0, 3, 2, 4], [0, 1, 2, 3, 4], 8); [INFO] [stdout] | --------------------------------------------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in a future release! [INFO] [stdout] = note: for more information, see issue #66145 [INFO] [stdout] = note: this warning originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: this method call currently resolves to `<&[T; N] as IntoIterator>::into_iter` (due to autoref coercions), but that might change in the future when `IntoIterator` impls for arrays are added. [INFO] [stdout] --> src/infrastructure/arranging/sequencing.rs:202:56 [INFO] [stdout] | [INFO] [stdout] 202 | let sequenced_packets: Vec<_> = before.into_iter() [INFO] [stdout] | ^^^^^^^^^ help: use `.iter()` instead of `.into_iter()` to avoid ambiguity: `iter` [INFO] [stdout] ... [INFO] [stdout] 216 | assert_sequence!([1, 3, 5, 4, 2], [1, 3, 5], 1); [INFO] [stdout] | ------------------------------------------------ in this macro invocation [INFO] [stdout] | [INFO] [stdout] = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in a future release! [INFO] [stdout] = note: for more information, see issue #66145 [INFO] [stdout] = note: this warning originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: this method call currently resolves to `<&[T; N] as IntoIterator>::into_iter` (due to autoref coercions), but that might change in the future when `IntoIterator` impls for arrays are added. [INFO] [stdout] --> src/infrastructure/arranging/sequencing.rs:202:56 [INFO] [stdout] | [INFO] [stdout] 202 | let sequenced_packets: Vec<_> = before.into_iter() [INFO] [stdout] | ^^^^^^^^^ help: use `.iter()` instead of `.into_iter()` to avoid ambiguity: `iter` [INFO] [stdout] ... [INFO] [stdout] 217 | assert_sequence!([1, 5, 4, 3, 2], [1, 5], 1); [INFO] [stdout] | --------------------------------------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in a future release! [INFO] [stdout] = note: for more information, see issue #66145 [INFO] [stdout] = note: this warning originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: this method call currently resolves to `<&[T; N] as IntoIterator>::into_iter` (due to autoref coercions), but that might change in the future when `IntoIterator` impls for arrays are added. [INFO] [stdout] --> src/infrastructure/arranging/sequencing.rs:202:56 [INFO] [stdout] | [INFO] [stdout] 202 | let sequenced_packets: Vec<_> = before.into_iter() [INFO] [stdout] | ^^^^^^^^^ help: use `.iter()` instead of `.into_iter()` to avoid ambiguity: `iter` [INFO] [stdout] ... [INFO] [stdout] 218 | assert_sequence!([5, 3, 4, 2, 1], [5], 1); [INFO] [stdout] | ------------------------------------------ in this macro invocation [INFO] [stdout] | [INFO] [stdout] = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in a future release! [INFO] [stdout] = note: for more information, see issue #66145 [INFO] [stdout] = note: this warning originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: this method call currently resolves to `<&[T; N] as IntoIterator>::into_iter` (due to autoref coercions), but that might change in the future when `IntoIterator` impls for arrays are added. [INFO] [stdout] --> src/infrastructure/arranging/sequencing.rs:202:56 [INFO] [stdout] | [INFO] [stdout] 202 | let sequenced_packets: Vec<_> = before.into_iter() [INFO] [stdout] | ^^^^^^^^^ help: use `.iter()` instead of `.into_iter()` to avoid ambiguity: `iter` [INFO] [stdout] ... [INFO] [stdout] 219 | assert_sequence!([4, 3, 2, 1, 5], [4, 5], 1); [INFO] [stdout] | --------------------------------------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in a future release! [INFO] [stdout] = note: for more information, see issue #66145 [INFO] [stdout] = note: this warning originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: this method call currently resolves to `<&[T; N] as IntoIterator>::into_iter` (due to autoref coercions), but that might change in the future when `IntoIterator` impls for arrays are added. [INFO] [stdout] --> src/infrastructure/arranging/sequencing.rs:202:56 [INFO] [stdout] | [INFO] [stdout] 202 | let sequenced_packets: Vec<_> = before.into_iter() [INFO] [stdout] | ^^^^^^^^^ help: use `.iter()` instead of `.into_iter()` to avoid ambiguity: `iter` [INFO] [stdout] ... [INFO] [stdout] 220 | assert_sequence!([2, 1, 4, 3, 5], [2, 4, 5], 1); [INFO] [stdout] | ------------------------------------------------ in this macro invocation [INFO] [stdout] | [INFO] [stdout] = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in a future release! [INFO] [stdout] = note: for more information, see issue #66145 [INFO] [stdout] = note: this warning originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: this method call currently resolves to `<&[T; N] as IntoIterator>::into_iter` (due to autoref coercions), but that might change in the future when `IntoIterator` impls for arrays are added. [INFO] [stdout] --> src/infrastructure/arranging/sequencing.rs:202:56 [INFO] [stdout] | [INFO] [stdout] 202 | let sequenced_packets: Vec<_> = before.into_iter() [INFO] [stdout] | ^^^^^^^^^ help: use `.iter()` instead of `.into_iter()` to avoid ambiguity: `iter` [INFO] [stdout] ... [INFO] [stdout] 221 | assert_sequence!([5, 2, 1, 4, 3], [5], 1); [INFO] [stdout] | ------------------------------------------ in this macro invocation [INFO] [stdout] | [INFO] [stdout] = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in a future release! [INFO] [stdout] = note: for more information, see issue #66145 [INFO] [stdout] = note: this warning originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: this method call currently resolves to `<&[T; N] as IntoIterator>::into_iter` (due to autoref coercions), but that might change in the future when `IntoIterator` impls for arrays are added. [INFO] [stdout] --> src/infrastructure/arranging/sequencing.rs:202:56 [INFO] [stdout] | [INFO] [stdout] 202 | let sequenced_packets: Vec<_> = before.into_iter() [INFO] [stdout] | ^^^^^^^^^ help: use `.iter()` instead of `.into_iter()` to avoid ambiguity: `iter` [INFO] [stdout] ... [INFO] [stdout] 222 | assert_sequence!([3, 2, 4, 1, 5], [3, 4, 5], 1); [INFO] [stdout] | ------------------------------------------------ in this macro invocation [INFO] [stdout] | [INFO] [stdout] = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in a future release! [INFO] [stdout] = note: for more information, see issue #66145 [INFO] [stdout] = note: this warning originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: this method call currently resolves to `<&[T; N] as IntoIterator>::into_iter` (due to autoref coercions), but that might change in the future when `IntoIterator` impls for arrays are added. [INFO] [stdout] --> src/infrastructure/arranging/sequencing.rs:202:56 [INFO] [stdout] | [INFO] [stdout] 202 | let sequenced_packets: Vec<_> = before.into_iter() [INFO] [stdout] | ^^^^^^^^^ help: use `.iter()` instead of `.into_iter()` to avoid ambiguity: `iter` [INFO] [stdout] ... [INFO] [stdout] 228 | assert_sequence!([1, 3, 5, 4, 2], [1, 3, 5], 1); [INFO] [stdout] | ------------------------------------------------ in this macro invocation [INFO] [stdout] | [INFO] [stdout] = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in a future release! [INFO] [stdout] = note: for more information, see issue #66145 [INFO] [stdout] = note: this warning originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: this method call currently resolves to `<&[T; N] as IntoIterator>::into_iter` (due to autoref coercions), but that might change in the future when `IntoIterator` impls for arrays are added. [INFO] [stdout] --> src/infrastructure/arranging/sequencing.rs:202:56 [INFO] [stdout] | [INFO] [stdout] 202 | let sequenced_packets: Vec<_> = before.into_iter() [INFO] [stdout] | ^^^^^^^^^ help: use `.iter()` instead of `.into_iter()` to avoid ambiguity: `iter` [INFO] [stdout] ... [INFO] [stdout] 229 | assert_sequence!([1, 5, 4, 3, 2], [1, 5], 2); [INFO] [stdout] | --------------------------------------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in a future release! [INFO] [stdout] = note: for more information, see issue #66145 [INFO] [stdout] = note: this warning originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: this method call currently resolves to `<&[T; N] as IntoIterator>::into_iter` (due to autoref coercions), but that might change in the future when `IntoIterator` impls for arrays are added. [INFO] [stdout] --> src/infrastructure/arranging/sequencing.rs:202:56 [INFO] [stdout] | [INFO] [stdout] 202 | let sequenced_packets: Vec<_> = before.into_iter() [INFO] [stdout] | ^^^^^^^^^ help: use `.iter()` instead of `.into_iter()` to avoid ambiguity: `iter` [INFO] [stdout] ... [INFO] [stdout] 230 | assert_sequence!([5, 3, 4, 2, 1], [5], 3); [INFO] [stdout] | ------------------------------------------ in this macro invocation [INFO] [stdout] | [INFO] [stdout] = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in a future release! [INFO] [stdout] = note: for more information, see issue #66145 [INFO] [stdout] = note: this warning originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: this method call currently resolves to `<&[T; N] as IntoIterator>::into_iter` (due to autoref coercions), but that might change in the future when `IntoIterator` impls for arrays are added. [INFO] [stdout] --> src/infrastructure/arranging/sequencing.rs:202:56 [INFO] [stdout] | [INFO] [stdout] 202 | let sequenced_packets: Vec<_> = before.into_iter() [INFO] [stdout] | ^^^^^^^^^ help: use `.iter()` instead of `.into_iter()` to avoid ambiguity: `iter` [INFO] [stdout] ... [INFO] [stdout] 231 | assert_sequence!([4, 3, 2, 1, 5], [4, 5], 4); [INFO] [stdout] | --------------------------------------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in a future release! [INFO] [stdout] = note: for more information, see issue #66145 [INFO] [stdout] = note: this warning originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: this method call currently resolves to `<&[T; N] as IntoIterator>::into_iter` (due to autoref coercions), but that might change in the future when `IntoIterator` impls for arrays are added. [INFO] [stdout] --> src/infrastructure/arranging/sequencing.rs:202:56 [INFO] [stdout] | [INFO] [stdout] 202 | let sequenced_packets: Vec<_> = before.into_iter() [INFO] [stdout] | ^^^^^^^^^ help: use `.iter()` instead of `.into_iter()` to avoid ambiguity: `iter` [INFO] [stdout] ... [INFO] [stdout] 232 | assert_sequence!([2, 1, 4, 3, 5], [2, 4, 5], 5); [INFO] [stdout] | ------------------------------------------------ in this macro invocation [INFO] [stdout] | [INFO] [stdout] = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in a future release! [INFO] [stdout] = note: for more information, see issue #66145 [INFO] [stdout] = note: this warning originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: this method call currently resolves to `<&[T; N] as IntoIterator>::into_iter` (due to autoref coercions), but that might change in the future when `IntoIterator` impls for arrays are added. [INFO] [stdout] --> src/infrastructure/arranging/sequencing.rs:202:56 [INFO] [stdout] | [INFO] [stdout] 202 | let sequenced_packets: Vec<_> = before.into_iter() [INFO] [stdout] | ^^^^^^^^^ help: use `.iter()` instead of `.into_iter()` to avoid ambiguity: `iter` [INFO] [stdout] ... [INFO] [stdout] 233 | assert_sequence!([5, 2, 1, 4, 3], [5], 6); [INFO] [stdout] | ------------------------------------------ in this macro invocation [INFO] [stdout] | [INFO] [stdout] = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in a future release! [INFO] [stdout] = note: for more information, see issue #66145 [INFO] [stdout] = note: this warning originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: this method call currently resolves to `<&[T; N] as IntoIterator>::into_iter` (due to autoref coercions), but that might change in the future when `IntoIterator` impls for arrays are added. [INFO] [stdout] --> src/infrastructure/arranging/sequencing.rs:202:56 [INFO] [stdout] | [INFO] [stdout] 202 | let sequenced_packets: Vec<_> = before.into_iter() [INFO] [stdout] | ^^^^^^^^^ help: use `.iter()` instead of `.into_iter()` to avoid ambiguity: `iter` [INFO] [stdout] ... [INFO] [stdout] 234 | assert_sequence!([3, 2, 4, 1, 5], [3, 4, 5], 7); [INFO] [stdout] | ------------------------------------------------ in this macro invocation [INFO] [stdout] | [INFO] [stdout] = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in a future release! [INFO] [stdout] = note: for more information, see issue #66145 [INFO] [stdout] = note: this warning originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: 31 warnings emitted [INFO] [stdout] [INFO] [stdout] [INFO] [stderr] Finished test [unoptimized + debuginfo] target(s) in 35.76s [INFO] running `Command { std: "docker" "inspect" "c6654b5547576d29a35a26024d518b9befca8b1ebd76a741a096687a46bb0e23", kill_on_drop: false }` [INFO] running `Command { std: "docker" "rm" "-f" "c6654b5547576d29a35a26024d518b9befca8b1ebd76a741a096687a46bb0e23", kill_on_drop: false }` [INFO] [stdout] c6654b5547576d29a35a26024d518b9befca8b1ebd76a741a096687a46bb0e23 [INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-12/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-12/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=warn" "-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" "rustops/crates-build-env@sha256:b8eeb62f26c39b23691079a6cb6de528d8e88b4d71a8f6b1d30f8ba7d9c16de9" "/opt/rustwide/cargo-home/bin/cargo" "+1.49.0" "test" "--frozen", kill_on_drop: false }` [INFO] [stderr] WARNING: Your kernel does not support swap limit capabilities or the cgroup is not mounted. Memory limited without swap. [INFO] [stdout] fe8bf9011165d709afd3de9ed801bf9c7f4ce1883834b978dbb98f3bf0559015 [INFO] running `Command { std: "docker" "start" "-a" "fe8bf9011165d709afd3de9ed801bf9c7f4ce1883834b978dbb98f3bf0559015", kill_on_drop: false }` [INFO] [stderr] warning: unused import: `Ipv4Addr` [INFO] [stderr] --> src/net/connection_manager.rs:212:15 [INFO] [stderr] | [INFO] [stderr] 212 | net::{Ipv4Addr, SocketAddr, SocketAddrV4}, [INFO] [stderr] | ^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = note: `#[warn(unused_imports)]` on by default [INFO] [stderr] [INFO] [stderr] warning: this method call currently resolves to `<&[T; N] as IntoIterator>::into_iter` (due to autoref coercions), but that might change in the future when `IntoIterator` impls for arrays are added. [INFO] [stderr] --> src/infrastructure/arranging/ordering.rs:447:51 [INFO] [stderr] | [INFO] [stderr] 447 | let ordered_packets : Vec<_> = before.into_iter() [INFO] [stderr] | ^^^^^^^^^ help: use `.iter()` instead of `.into_iter()` to avoid ambiguity: `iter` [INFO] [stderr] ... [INFO] [stderr] 465 | assert_order!([0, 2, 4, 3, 1], [0, 1, 2, 3, 4], 1); [INFO] [stderr] | --------------------------------------------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: `#[warn(array_into_iter)]` on by default [INFO] [stderr] = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in a future release! [INFO] [stderr] = note: for more information, see issue #66145 [INFO] [stderr] = note: this warning originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: this method call currently resolves to `<&[T; N] as IntoIterator>::into_iter` (due to autoref coercions), but that might change in the future when `IntoIterator` impls for arrays are added. [INFO] [stderr] --> src/infrastructure/arranging/ordering.rs:447:51 [INFO] [stderr] | [INFO] [stderr] 447 | let ordered_packets : Vec<_> = before.into_iter() [INFO] [stderr] | ^^^^^^^^^ help: use `.iter()` instead of `.into_iter()` to avoid ambiguity: `iter` [INFO] [stderr] ... [INFO] [stderr] 466 | assert_order!([0, 4, 3, 2, 1], [0, 1, 2, 3, 4], 1); [INFO] [stderr] | --------------------------------------------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in a future release! [INFO] [stderr] = note: for more information, see issue #66145 [INFO] [stderr] = note: this warning originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: this method call currently resolves to `<&[T; N] as IntoIterator>::into_iter` (due to autoref coercions), but that might change in the future when `IntoIterator` impls for arrays are added. [INFO] [stderr] --> src/infrastructure/arranging/ordering.rs:447:51 [INFO] [stderr] | [INFO] [stderr] 447 | let ordered_packets : Vec<_> = before.into_iter() [INFO] [stderr] | ^^^^^^^^^ help: use `.iter()` instead of `.into_iter()` to avoid ambiguity: `iter` [INFO] [stderr] ... [INFO] [stderr] 467 | assert_order!([4, 2, 3, 1, 0], [0, 1, 2, 3, 4], 1); [INFO] [stderr] | --------------------------------------------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in a future release! [INFO] [stderr] = note: for more information, see issue #66145 [INFO] [stderr] = note: this warning originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: this method call currently resolves to `<&[T; N] as IntoIterator>::into_iter` (due to autoref coercions), but that might change in the future when `IntoIterator` impls for arrays are added. [INFO] [stderr] --> src/infrastructure/arranging/ordering.rs:447:51 [INFO] [stderr] | [INFO] [stderr] 447 | let ordered_packets : Vec<_> = before.into_iter() [INFO] [stderr] | ^^^^^^^^^ help: use `.iter()` instead of `.into_iter()` to avoid ambiguity: `iter` [INFO] [stderr] ... [INFO] [stderr] 468 | assert_order!([3, 2, 1, 0, 4], [0, 1, 2, 3, 4], 1); [INFO] [stderr] | --------------------------------------------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in a future release! [INFO] [stderr] = note: for more information, see issue #66145 [INFO] [stderr] = note: this warning originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: this method call currently resolves to `<&[T; N] as IntoIterator>::into_iter` (due to autoref coercions), but that might change in the future when `IntoIterator` impls for arrays are added. [INFO] [stderr] --> src/infrastructure/arranging/ordering.rs:447:51 [INFO] [stderr] | [INFO] [stderr] 447 | let ordered_packets : Vec<_> = before.into_iter() [INFO] [stderr] | ^^^^^^^^^ help: use `.iter()` instead of `.into_iter()` to avoid ambiguity: `iter` [INFO] [stderr] ... [INFO] [stderr] 469 | assert_order!([1, 0, 3, 2, 4], [0, 1, 2, 3, 4], 1); [INFO] [stderr] | --------------------------------------------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in a future release! [INFO] [stderr] = note: for more information, see issue #66145 [INFO] [stderr] = note: this warning originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: this method call currently resolves to `<&[T; N] as IntoIterator>::into_iter` (due to autoref coercions), but that might change in the future when `IntoIterator` impls for arrays are added. [INFO] [stderr] --> src/infrastructure/arranging/ordering.rs:447:51 [INFO] [stderr] | [INFO] [stderr] 447 | let ordered_packets : Vec<_> = before.into_iter() [INFO] [stderr] | ^^^^^^^^^ help: use `.iter()` instead of `.into_iter()` to avoid ambiguity: `iter` [INFO] [stderr] ... [INFO] [stderr] 470 | assert_order!([4, 1, 0, 3, 2], [0, 1, 2, 3, 4], 1); [INFO] [stderr] | --------------------------------------------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in a future release! [INFO] [stderr] = note: for more information, see issue #66145 [INFO] [stderr] = note: this warning originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: this method call currently resolves to `<&[T; N] as IntoIterator>::into_iter` (due to autoref coercions), but that might change in the future when `IntoIterator` impls for arrays are added. [INFO] [stderr] --> src/infrastructure/arranging/ordering.rs:447:51 [INFO] [stderr] | [INFO] [stderr] 447 | let ordered_packets : Vec<_> = before.into_iter() [INFO] [stderr] | ^^^^^^^^^ help: use `.iter()` instead of `.into_iter()` to avoid ambiguity: `iter` [INFO] [stderr] ... [INFO] [stderr] 471 | assert_order!([2, 1, 3, 0, 4], [0, 1, 2, 3, 4], 1); [INFO] [stderr] | --------------------------------------------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in a future release! [INFO] [stderr] = note: for more information, see issue #66145 [INFO] [stderr] = note: this warning originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: this method call currently resolves to `<&[T; N] as IntoIterator>::into_iter` (due to autoref coercions), but that might change in the future when `IntoIterator` impls for arrays are added. [INFO] [stderr] --> src/infrastructure/arranging/ordering.rs:447:51 [INFO] [stderr] | [INFO] [stderr] 447 | let ordered_packets : Vec<_> = before.into_iter() [INFO] [stderr] | ^^^^^^^^^ help: use `.iter()` instead of `.into_iter()` to avoid ambiguity: `iter` [INFO] [stderr] ... [INFO] [stderr] 472 | assert_order!([1, 0, 3, 2, 4], [0, 1, 2, 3, 4], 1); [INFO] [stderr] | --------------------------------------------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in a future release! [INFO] [stderr] = note: for more information, see issue #66145 [INFO] [stderr] = note: this warning originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: this method call currently resolves to `<&[T; N] as IntoIterator>::into_iter` (due to autoref coercions), but that might change in the future when `IntoIterator` impls for arrays are added. [INFO] [stderr] --> src/infrastructure/arranging/ordering.rs:447:51 [INFO] [stderr] | [INFO] [stderr] 447 | let ordered_packets : Vec<_> = before.into_iter() [INFO] [stderr] | ^^^^^^^^^ help: use `.iter()` instead of `.into_iter()` to avoid ambiguity: `iter` [INFO] [stderr] ... [INFO] [stderr] 478 | assert_order!([0, 2, 4, 3, 1], [0, 1, 2, 3, 4], 1); [INFO] [stderr] | --------------------------------------------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in a future release! [INFO] [stderr] = note: for more information, see issue #66145 [INFO] [stderr] = note: this warning originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: this method call currently resolves to `<&[T; N] as IntoIterator>::into_iter` (due to autoref coercions), but that might change in the future when `IntoIterator` impls for arrays are added. [INFO] [stderr] --> src/infrastructure/arranging/ordering.rs:447:51 [INFO] [stderr] | [INFO] [stderr] 447 | let ordered_packets : Vec<_> = before.into_iter() [INFO] [stderr] | ^^^^^^^^^ help: use `.iter()` instead of `.into_iter()` to avoid ambiguity: `iter` [INFO] [stderr] ... [INFO] [stderr] 479 | assert_order!([0, 4, 3, 2, 1], [0, 1, 2, 3, 4], 2); [INFO] [stderr] | --------------------------------------------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in a future release! [INFO] [stderr] = note: for more information, see issue #66145 [INFO] [stderr] = note: this warning originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: this method call currently resolves to `<&[T; N] as IntoIterator>::into_iter` (due to autoref coercions), but that might change in the future when `IntoIterator` impls for arrays are added. [INFO] [stderr] --> src/infrastructure/arranging/ordering.rs:447:51 [INFO] [stderr] | [INFO] [stderr] 447 | let ordered_packets : Vec<_> = before.into_iter() [INFO] [stderr] | ^^^^^^^^^ help: use `.iter()` instead of `.into_iter()` to avoid ambiguity: `iter` [INFO] [stderr] ... [INFO] [stderr] 480 | assert_order!([4, 2, 3, 1, 0], [0, 1, 2, 3, 4], 3); [INFO] [stderr] | --------------------------------------------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in a future release! [INFO] [stderr] = note: for more information, see issue #66145 [INFO] [stderr] = note: this warning originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: this method call currently resolves to `<&[T; N] as IntoIterator>::into_iter` (due to autoref coercions), but that might change in the future when `IntoIterator` impls for arrays are added. [INFO] [stderr] --> src/infrastructure/arranging/ordering.rs:447:51 [INFO] [stderr] | [INFO] [stderr] 447 | let ordered_packets : Vec<_> = before.into_iter() [INFO] [stderr] | ^^^^^^^^^ help: use `.iter()` instead of `.into_iter()` to avoid ambiguity: `iter` [INFO] [stderr] ... [INFO] [stderr] 481 | assert_order!([3, 2, 1, 0, 4], [0, 1, 2, 3, 4], 4); [INFO] [stderr] | --------------------------------------------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in a future release! [INFO] [stderr] = note: for more information, see issue #66145 [INFO] [stderr] = note: this warning originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: this method call currently resolves to `<&[T; N] as IntoIterator>::into_iter` (due to autoref coercions), but that might change in the future when `IntoIterator` impls for arrays are added. [INFO] [stderr] --> src/infrastructure/arranging/ordering.rs:447:51 [INFO] [stderr] | [INFO] [stderr] 447 | let ordered_packets : Vec<_> = before.into_iter() [INFO] [stderr] | ^^^^^^^^^ help: use `.iter()` instead of `.into_iter()` to avoid ambiguity: `iter` [INFO] [stderr] ... [INFO] [stderr] 482 | assert_order!([1, 0, 3, 2, 4], [0, 1, 2, 3, 4], 5); [INFO] [stderr] | --------------------------------------------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in a future release! [INFO] [stderr] = note: for more information, see issue #66145 [INFO] [stderr] = note: this warning originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: this method call currently resolves to `<&[T; N] as IntoIterator>::into_iter` (due to autoref coercions), but that might change in the future when `IntoIterator` impls for arrays are added. [INFO] [stderr] --> src/infrastructure/arranging/ordering.rs:447:51 [INFO] [stderr] | [INFO] [stderr] 447 | let ordered_packets : Vec<_> = before.into_iter() [INFO] [stderr] | ^^^^^^^^^ help: use `.iter()` instead of `.into_iter()` to avoid ambiguity: `iter` [INFO] [stderr] ... [INFO] [stderr] 483 | assert_order!([4, 1, 0, 3, 2], [0, 1, 2, 3, 4], 6); [INFO] [stderr] | --------------------------------------------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in a future release! [INFO] [stderr] = note: for more information, see issue #66145 [INFO] [stderr] = note: this warning originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: this method call currently resolves to `<&[T; N] as IntoIterator>::into_iter` (due to autoref coercions), but that might change in the future when `IntoIterator` impls for arrays are added. [INFO] [stderr] --> src/infrastructure/arranging/ordering.rs:447:51 [INFO] [stderr] | [INFO] [stderr] 447 | let ordered_packets : Vec<_> = before.into_iter() [INFO] [stderr] | ^^^^^^^^^ help: use `.iter()` instead of `.into_iter()` to avoid ambiguity: `iter` [INFO] [stderr] ... [INFO] [stderr] 484 | assert_order!([2, 1, 3, 0, 4], [0, 1, 2, 3, 4], 7); [INFO] [stderr] | --------------------------------------------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in a future release! [INFO] [stderr] = note: for more information, see issue #66145 [INFO] [stderr] = note: this warning originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: this method call currently resolves to `<&[T; N] as IntoIterator>::into_iter` (due to autoref coercions), but that might change in the future when `IntoIterator` impls for arrays are added. [INFO] [stderr] --> src/infrastructure/arranging/ordering.rs:447:51 [INFO] [stderr] | [INFO] [stderr] 447 | let ordered_packets : Vec<_> = before.into_iter() [INFO] [stderr] | ^^^^^^^^^ help: use `.iter()` instead of `.into_iter()` to avoid ambiguity: `iter` [INFO] [stderr] ... [INFO] [stderr] 485 | assert_order!([1, 0, 3, 2, 4], [0, 1, 2, 3, 4], 8); [INFO] [stderr] | --------------------------------------------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in a future release! [INFO] [stderr] = note: for more information, see issue #66145 [INFO] [stderr] = note: this warning originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: this method call currently resolves to `<&[T; N] as IntoIterator>::into_iter` (due to autoref coercions), but that might change in the future when `IntoIterator` impls for arrays are added. [INFO] [stderr] --> src/infrastructure/arranging/sequencing.rs:202:56 [INFO] [stderr] | [INFO] [stderr] 202 | let sequenced_packets: Vec<_> = before.into_iter() [INFO] [stderr] | ^^^^^^^^^ help: use `.iter()` instead of `.into_iter()` to avoid ambiguity: `iter` [INFO] [stderr] ... [INFO] [stderr] 216 | assert_sequence!([1, 3, 5, 4, 2], [1, 3, 5], 1); [INFO] [stderr] | ------------------------------------------------ in this macro invocation [INFO] [stderr] | [INFO] [stderr] = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in a future release! [INFO] [stderr] = note: for more information, see issue #66145 [INFO] [stderr] = note: this warning originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: this method call currently resolves to `<&[T; N] as IntoIterator>::into_iter` (due to autoref coercions), but that might change in the future when `IntoIterator` impls for arrays are added. [INFO] [stderr] --> src/infrastructure/arranging/sequencing.rs:202:56 [INFO] [stderr] | [INFO] [stderr] 202 | let sequenced_packets: Vec<_> = before.into_iter() [INFO] [stderr] | ^^^^^^^^^ help: use `.iter()` instead of `.into_iter()` to avoid ambiguity: `iter` [INFO] [stderr] ... [INFO] [stderr] 217 | assert_sequence!([1, 5, 4, 3, 2], [1, 5], 1); [INFO] [stderr] | --------------------------------------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in a future release! [INFO] [stderr] = note: for more information, see issue #66145 [INFO] [stderr] = note: this warning originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: this method call currently resolves to `<&[T; N] as IntoIterator>::into_iter` (due to autoref coercions), but that might change in the future when `IntoIterator` impls for arrays are added. [INFO] [stderr] --> src/infrastructure/arranging/sequencing.rs:202:56 [INFO] [stderr] | [INFO] [stderr] 202 | let sequenced_packets: Vec<_> = before.into_iter() [INFO] [stderr] | ^^^^^^^^^ help: use `.iter()` instead of `.into_iter()` to avoid ambiguity: `iter` [INFO] [stderr] ... [INFO] [stderr] 218 | assert_sequence!([5, 3, 4, 2, 1], [5], 1); [INFO] [stderr] | ------------------------------------------ in this macro invocation [INFO] [stderr] | [INFO] [stderr] = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in a future release! [INFO] [stderr] = note: for more information, see issue #66145 [INFO] [stderr] = note: this warning originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: this method call currently resolves to `<&[T; N] as IntoIterator>::into_iter` (due to autoref coercions), but that might change in the future when `IntoIterator` impls for arrays are added. [INFO] [stderr] --> src/infrastructure/arranging/sequencing.rs:202:56 [INFO] [stderr] | [INFO] [stderr] 202 | let sequenced_packets: Vec<_> = before.into_iter() [INFO] [stderr] | ^^^^^^^^^ help: use `.iter()` instead of `.into_iter()` to avoid ambiguity: `iter` [INFO] [stderr] ... [INFO] [stderr] 219 | assert_sequence!([4, 3, 2, 1, 5], [4, 5], 1); [INFO] [stderr] | --------------------------------------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in a future release! [INFO] [stderr] = note: for more information, see issue #66145 [INFO] [stderr] = note: this warning originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: this method call currently resolves to `<&[T; N] as IntoIterator>::into_iter` (due to autoref coercions), but that might change in the future when `IntoIterator` impls for arrays are added. [INFO] [stderr] --> src/infrastructure/arranging/sequencing.rs:202:56 [INFO] [stderr] | [INFO] [stderr] 202 | let sequenced_packets: Vec<_> = before.into_iter() [INFO] [stderr] | ^^^^^^^^^ help: use `.iter()` instead of `.into_iter()` to avoid ambiguity: `iter` [INFO] [stderr] ... [INFO] [stderr] 220 | assert_sequence!([2, 1, 4, 3, 5], [2, 4, 5], 1); [INFO] [stderr] | ------------------------------------------------ in this macro invocation [INFO] [stderr] | [INFO] [stderr] = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in a future release! [INFO] [stderr] = note: for more information, see issue #66145 [INFO] [stderr] = note: this warning originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: this method call currently resolves to `<&[T; N] as IntoIterator>::into_iter` (due to autoref coercions), but that might change in the future when `IntoIterator` impls for arrays are added. [INFO] [stderr] --> src/infrastructure/arranging/sequencing.rs:202:56 [INFO] [stderr] | [INFO] [stderr] 202 | let sequenced_packets: Vec<_> = before.into_iter() [INFO] [stderr] | ^^^^^^^^^ help: use `.iter()` instead of `.into_iter()` to avoid ambiguity: `iter` [INFO] [stderr] ... [INFO] [stderr] 221 | assert_sequence!([5, 2, 1, 4, 3], [5], 1); [INFO] [stderr] | ------------------------------------------ in this macro invocation [INFO] [stderr] | [INFO] [stderr] = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in a future release! [INFO] [stderr] = note: for more information, see issue #66145 [INFO] [stderr] = note: this warning originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: this method call currently resolves to `<&[T; N] as IntoIterator>::into_iter` (due to autoref coercions), but that might change in the future when `IntoIterator` impls for arrays are added. [INFO] [stderr] --> src/infrastructure/arranging/sequencing.rs:202:56 [INFO] [stderr] | [INFO] [stderr] 202 | let sequenced_packets: Vec<_> = before.into_iter() [INFO] [stderr] | ^^^^^^^^^ help: use `.iter()` instead of `.into_iter()` to avoid ambiguity: `iter` [INFO] [stderr] ... [INFO] [stderr] 222 | assert_sequence!([3, 2, 4, 1, 5], [3, 4, 5], 1); [INFO] [stderr] | ------------------------------------------------ in this macro invocation [INFO] [stderr] | [INFO] [stderr] = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in a future release! [INFO] [stderr] = note: for more information, see issue #66145 [INFO] [stderr] = note: this warning originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: this method call currently resolves to `<&[T; N] as IntoIterator>::into_iter` (due to autoref coercions), but that might change in the future when `IntoIterator` impls for arrays are added. [INFO] [stderr] --> src/infrastructure/arranging/sequencing.rs:202:56 [INFO] [stderr] | [INFO] [stderr] 202 | let sequenced_packets: Vec<_> = before.into_iter() [INFO] [stderr] | ^^^^^^^^^ help: use `.iter()` instead of `.into_iter()` to avoid ambiguity: `iter` [INFO] [stderr] ... [INFO] [stderr] 228 | assert_sequence!([1, 3, 5, 4, 2], [1, 3, 5], 1); [INFO] [stderr] | ------------------------------------------------ in this macro invocation [INFO] [stderr] | [INFO] [stderr] = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in a future release! [INFO] [stderr] = note: for more information, see issue #66145 [INFO] [stderr] = note: this warning originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: this method call currently resolves to `<&[T; N] as IntoIterator>::into_iter` (due to autoref coercions), but that might change in the future when `IntoIterator` impls for arrays are added. [INFO] [stderr] --> src/infrastructure/arranging/sequencing.rs:202:56 [INFO] [stderr] | [INFO] [stderr] 202 | let sequenced_packets: Vec<_> = before.into_iter() [INFO] [stderr] | ^^^^^^^^^ help: use `.iter()` instead of `.into_iter()` to avoid ambiguity: `iter` [INFO] [stderr] ... [INFO] [stderr] 229 | assert_sequence!([1, 5, 4, 3, 2], [1, 5], 2); [INFO] [stderr] | --------------------------------------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in a future release! [INFO] [stderr] = note: for more information, see issue #66145 [INFO] [stderr] = note: this warning originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: this method call currently resolves to `<&[T; N] as IntoIterator>::into_iter` (due to autoref coercions), but that might change in the future when `IntoIterator` impls for arrays are added. [INFO] [stderr] --> src/infrastructure/arranging/sequencing.rs:202:56 [INFO] [stderr] | [INFO] [stderr] 202 | let sequenced_packets: Vec<_> = before.into_iter() [INFO] [stderr] | ^^^^^^^^^ help: use `.iter()` instead of `.into_iter()` to avoid ambiguity: `iter` [INFO] [stderr] ... [INFO] [stderr] 230 | assert_sequence!([5, 3, 4, 2, 1], [5], 3); [INFO] [stderr] | ------------------------------------------ in this macro invocation [INFO] [stderr] | [INFO] [stderr] = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in a future release! [INFO] [stderr] = note: for more information, see issue #66145 [INFO] [stderr] = note: this warning originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: this method call currently resolves to `<&[T; N] as IntoIterator>::into_iter` (due to autoref coercions), but that might change in the future when `IntoIterator` impls for arrays are added. [INFO] [stderr] --> src/infrastructure/arranging/sequencing.rs:202:56 [INFO] [stderr] | [INFO] [stderr] 202 | let sequenced_packets: Vec<_> = before.into_iter() [INFO] [stderr] | ^^^^^^^^^ help: use `.iter()` instead of `.into_iter()` to avoid ambiguity: `iter` [INFO] [stderr] ... [INFO] [stderr] 231 | assert_sequence!([4, 3, 2, 1, 5], [4, 5], 4); [INFO] [stderr] | --------------------------------------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in a future release! [INFO] [stderr] = note: for more information, see issue #66145 [INFO] [stderr] = note: this warning originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: this method call currently resolves to `<&[T; N] as IntoIterator>::into_iter` (due to autoref coercions), but that might change in the future when `IntoIterator` impls for arrays are added. [INFO] [stderr] --> src/infrastructure/arranging/sequencing.rs:202:56 [INFO] [stderr] | [INFO] [stderr] 202 | let sequenced_packets: Vec<_> = before.into_iter() [INFO] [stderr] | ^^^^^^^^^ help: use `.iter()` instead of `.into_iter()` to avoid ambiguity: `iter` [INFO] [stderr] ... [INFO] [stderr] 232 | assert_sequence!([2, 1, 4, 3, 5], [2, 4, 5], 5); [INFO] [stderr] | ------------------------------------------------ in this macro invocation [INFO] [stderr] | [INFO] [stderr] = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in a future release! [INFO] [stderr] = note: for more information, see issue #66145 [INFO] [stderr] = note: this warning originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: this method call currently resolves to `<&[T; N] as IntoIterator>::into_iter` (due to autoref coercions), but that might change in the future when `IntoIterator` impls for arrays are added. [INFO] [stderr] --> src/infrastructure/arranging/sequencing.rs:202:56 [INFO] [stderr] | [INFO] [stderr] 202 | let sequenced_packets: Vec<_> = before.into_iter() [INFO] [stderr] | ^^^^^^^^^ help: use `.iter()` instead of `.into_iter()` to avoid ambiguity: `iter` [INFO] [stderr] ... [INFO] [stderr] 233 | assert_sequence!([5, 2, 1, 4, 3], [5], 6); [INFO] [stderr] | ------------------------------------------ in this macro invocation [INFO] [stderr] | [INFO] [stderr] = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in a future release! [INFO] [stderr] = note: for more information, see issue #66145 [INFO] [stderr] = note: this warning originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: this method call currently resolves to `<&[T; N] as IntoIterator>::into_iter` (due to autoref coercions), but that might change in the future when `IntoIterator` impls for arrays are added. [INFO] [stderr] --> src/infrastructure/arranging/sequencing.rs:202:56 [INFO] [stderr] | [INFO] [stderr] 202 | let sequenced_packets: Vec<_> = before.into_iter() [INFO] [stderr] | ^^^^^^^^^ help: use `.iter()` instead of `.into_iter()` to avoid ambiguity: `iter` [INFO] [stderr] ... [INFO] [stderr] 234 | assert_sequence!([3, 2, 4, 1, 5], [3, 4, 5], 7); [INFO] [stderr] | ------------------------------------------------ in this macro invocation [INFO] [stderr] | [INFO] [stderr] = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in a future release! [INFO] [stderr] = note: for more information, see issue #66145 [INFO] [stderr] = note: this warning originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: 31 warnings emitted [INFO] [stderr] [INFO] [stderr] warning: unused variable: `client_addr` [INFO] [stderr] --> tests/basic_socket_test.rs:38:9 [INFO] [stderr] | [INFO] [stderr] 38 | let client_addr = client.local_addr().unwrap(); [INFO] [stderr] | ^^^^^^^^^^^ help: if this is intentional, prefix it with an underscore: `_client_addr` [INFO] [stderr] | [INFO] [stderr] = note: `#[warn(unused_variables)]` on by default [INFO] [stderr] [INFO] [stderr] warning: 1 warning emitted [INFO] [stderr] [INFO] [stderr] Finished test [unoptimized + debuginfo] target(s) in 0.20s [INFO] [stderr] Running /opt/rustwide/target/debug/deps/laminar-79a3169b847291c3 [INFO] [stdout] [INFO] [stdout] running 106 tests [INFO] [stdout] test error::tests::able_to_box_errors ... ok [INFO] [stdout] test infrastructure::acknowledgment::test::ack_bitfield_with_some_values ... ok [INFO] [stdout] test infrastructure::acknowledgment::test::ack_bitfield_with_empty_receive ... ok [INFO] [stdout] test infrastructure::acknowledgment::test::processing_a_full_set_of_packets ... ok [INFO] [stdout] test infrastructure::acknowledgment::test::test_process_outgoing ... ok [INFO] [stdout] test infrastructure::arranging::ordering::tests::expect_right_order ... ok [INFO] [stdout] test infrastructure::acknowledgment::test::local_seq_num_wraps_on_overflow ... ok [INFO] [stdout] test infrastructure::acknowledgment::test::remote_ack_seq_must_never_be_less_than_prior_wrap_boundary ... ok [INFO] [stdout] test infrastructure::arranging::ordering::tests::can_iterate ... ok [INFO] [stdout] test infrastructure::acknowledgment::test::remote_seq_num_will_be_updated ... ok [INFO] [stdout] test infrastructure::acknowledgment::test::packet_is_not_acked ... ok [INFO] [stdout] test infrastructure::acknowledgment::test::increment_local_seq_num_on_process_outgoing ... ok [INFO] [stdout] test infrastructure::arranging::ordering::tests::u16_forward_half ... ok [INFO] [stdout] test infrastructure::arranging::sequencing::tests::can_sequence ... ok [INFO] [stdout] test infrastructure::arranging::sequencing::tests::create_existing_stream ... ok [INFO] [stdout] test infrastructure::acknowledgment::test::acking_many_packets_with_packet_drop ... ok [INFO] [stdout] test infrastructure::acknowledgment::test::remote_ack_seq_must_never_be_less_than_prior ... ok [INFO] [stdout] test infrastructure::arranging::sequencing::tests::sequence_on_multiple_streams ... ok [INFO] [stdout] test infrastructure::arranging::ordering::tests::create_existing_stream ... ok [INFO] [stdout] test infrastructure::arranging::ordering::tests::create_stream ... ok [INFO] [stdout] test infrastructure::arranging::ordering::tests::packet_wraps_around_offset ... ok [INFO] [stdout] test infrastructure::arranging::sequencing::tests::create_stream ... ok [INFO] [stdout] test infrastructure::fragmenter::test::expect_right_number_of_fragments ... ok [INFO] [stdout] test infrastructure::arranging::ordering::tests::order_on_multiple_streams ... ok [INFO] [stdout] test infrastructure::arranging::ordering::tests::exactly_half_u16_packet_is_stored ... ok [INFO] [stdout] test infrastructure::congestion::test::congestion_entry_created ... ok [INFO] [stdout] test infrastructure::congestion::test::rtt_value_is_updated ... ok [INFO] [stdout] test infrastructure::acknowledgment::test::acking_500_packets_without_packet_drop ... ok [INFO] [stdout] test net::connection_manager::tests::initial_sequenced_is_resent ... ok [INFO] [stdout] test net::connection_manager::tests::manual_polling_socket ... ok [INFO] [stdout] test net::quality::test::convert_duration_to_milliseconds_test ... ok [INFO] [stdout] test net::connection_manager::tests::heartbeats_work ... ok [INFO] [stdout] test net::quality::test::smooth_out_rtt ... ok [INFO] [stdout] test net::quality::test::test_create_connection ... ok [INFO] [stdout] test net::virtual_connection::tests::assure_correct_processing_of_incoming ... ok [INFO] [stdout] test net::connection_manager::tests::do_not_duplicate_sequenced_packets_when_received ... ok [INFO] [stdout] test net::connection_manager::tests::initial_packet_is_resent ... ok [INFO] [stdout] test net::connection_manager::tests::fragmented_ordered_gets_acked ... ok [INFO] [stdout] test net::virtual_connection::tests::assure_right_fragmentation ... ok [INFO] [stdout] test net::virtual_connection::tests::assure_right_sequencing ... ok [INFO] [stdout] test net::virtual_connection::tests::assure_right_ordering ... ok [INFO] [stdout] test net::connection_manager::tests::initial_ordered_is_resent ... ok [INFO] [stdout] test net::virtual_connection::tests::fragmentation_send_returns_right_size ... ok [INFO] [stdout] test net::virtual_connection::tests::ensure_input_header_data_does_not_access_out_of_bounds ... ok [INFO] [stdout] test net::connection_manager::tests::sequenced_packets_pathological_case ... ok [INFO] [stdout] test net::virtual_connection::tests::set_last_sent_and_last_heard_when_processing ... ok [INFO] [stdout] test packet::enums::tests::assure_parsing_delivery_guarantee ... ok [INFO] [stdout] test net::virtual_connection::tests::send_returns_right_size ... ok [INFO] [stdout] test packet::enums::tests::assure_parsing_packet_type ... ok [INFO] [stdout] test packet::header::acked_packet_header::tests::deserialize ... ok [INFO] [stdout] test packet::header::acked_packet_header::tests::serialize ... ok [INFO] [stdout] test packet::enums::tests::assure_parsing_ordering_guarantee ... ok [INFO] [stdout] test packet::header::acked_packet_header::tests::size ... ok [INFO] [stdout] test net::virtual_connection::tests::sending_large_unreliable_packet_should_fail ... ok [INFO] [stdout] test packet::header::arranging_header::tests::deserialize ... ok [INFO] [stdout] test packet::header::arranging_header::tests::serialize ... ok [INFO] [stdout] test packet::header::arranging_header::tests::size ... ok [INFO] [stdout] test net::connection_manager::tests::multiple_sends_should_start_sending_dropped ... ok [INFO] [stdout] test packet::header::standard_header::tests::deserialize ... ok [INFO] [stdout] test packet::header::fragment_header::tests::deserialize ... ok [INFO] [stdout] test packet::header::fragment_header::tests::serialize ... ok [INFO] [stdout] test net::virtual_connection::tests::expect_fragmentation ... ok [INFO] [stdout] test packet::outgoing::tests::assure_creation_acknowledgment_header ... ok [INFO] [stdout] test packet::header::standard_header::tests::size ... ok [INFO] [stdout] test packet::outgoing::tests::assure_creation_fragment_header ... ok [INFO] [stdout] test packet::outgoing::tests::assure_creation_arranging_header ... ok [INFO] [stdout] test packet::packet_reader::tests::assure_read_acknowledgment_header ... ok [INFO] [stdout] test packet::packet_reader::tests::assure_read_fragment_header ... ok [INFO] [stdout] test packet::header::fragment_header::tests::size ... ok [INFO] [stdout] test packet::outgoing::tests::assure_creation_default_header ... ok [INFO] [stdout] test packet::header::standard_header::tests::serialize ... ok [INFO] [stdout] test packet::packet_reader::tests::assure_read_unreliable_sequenced_header ... ok [INFO] [stdout] test packet::packet_reader::tests::can_read_bytes ... ok [INFO] [stdout] test packet::packet_structure::tests::assure_creation_reliable ... ok [INFO] [stdout] test packet::packet_reader::tests::expect_read_error ... ok [INFO] [stdout] test packet::packet_structure::tests::assure_creation_reliable_sequence ... ok [INFO] [stdout] test packet::packet_reader::tests::assure_read_reliable_unordered_header ... ok [INFO] [stdout] test packet::packet_structure::tests::assure_creation_unreliable_packet ... ok [INFO] [stdout] test packet::packet_reader::tests::assure_read_reliable_ordered_header ... ok [INFO] [stdout] test packet::packet_structure::tests::assure_creation_unreliable_sequenced ... ok [INFO] [stdout] test protocol_version::test::get_version ... ok [INFO] [stdout] test protocol_version::test::not_valid_version ... ok [INFO] [stdout] test protocol_version::test::valid_version ... ok [INFO] [stdout] test sequence_buffer::tests::ensure_entries_and_entry_sequences_are_the_same_size ... ok [INFO] [stdout] test sequence_buffer::tests::insert_into_buffer_old_entry_test ... ok [INFO] [stdout] test sequence_buffer::tests::insert_into_buffer_test ... ok [INFO] [stdout] test sequence_buffer::tests::max_sequence_number_should_not_exist_by_default ... ok [INFO] [stdout] test packet::packet_reader::tests::assure_read_standard_header ... ok [INFO] [stdout] test packet::packet_structure::tests::assure_creation_reliable_ordered ... ok [INFO] [stdout] test sequence_buffer::tests::normal_inserts_should_fill_buffer ... ok [INFO] [stdout] test sequence_buffer::tests::older_sequence_numbers_arent_inserted ... ok [INFO] [stdout] test protocol_version::test::get_crc16 ... ok [INFO] [stdout] test sequence_buffer::tests::new_sequence_nums_evict_old_ones ... ok [INFO] [stdout] test sequence_buffer::tests::test_sequence_comparisons_than ... ok [INFO] [stdout] test net::connection_manager::tests::disconnect_event_occurs ... ok [INFO] [stdout] test sequence_buffer::tests::remove_from_buffer_test ... ok [INFO] [stdout] test net::connection_manager::tests::can_send_and_receive ... ok [INFO] [stdout] test net::connection_manager::tests::connect_event_occurs ... ok [INFO] [stdout] test net::virtual_connection::tests::assure_correct_outgoing_processing ... ok [INFO] [stdout] test net::connection_manager::tests::using_sender_and_receiver ... ok [INFO] [stdout] test net::virtual_connection::tests::assure_right_header_size ... ok [INFO] [stdout] test net::connection_manager::tests::receiving_does_not_allow_denial_of_service ... ok [INFO] [stdout] test net::connection_manager::tests::really_bad_network_keeps_chugging_along ... ok [INFO] [stdout] test net::connection_manager::tests::do_not_panic_on_arbitrary_packets ... ok [INFO] [stdout] test net::virtual_connection::tests::ordered_16_bit_overflow ... ok [INFO] [stdout] test net::connection_manager::tests::more_than_65536_sequenced_packets ... ok [INFO] [stderr] Running /opt/rustwide/target/debug/deps/basic_socket_test-c247553d70b64455 [INFO] [stdout] [INFO] [stdout] test result: ok. 106 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] running 3 tests [INFO] [stdout] test local_addr ... ok [INFO] [stdout] test binding_to_any ... ok [INFO] [stdout] test blocking_sender_and_receiver ... ok [INFO] [stdout] [INFO] [stdout] test result: ok. 3 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out [INFO] [stdout] [INFO] [stderr] Running /opt/rustwide/target/debug/deps/fragmentation_packets_test-6ca646195e42402a [INFO] [stdout] [INFO] [stderr] Running /opt/rustwide/target/debug/deps/unreliable_packets_test-efd4f3b9efae4438 [INFO] [stdout] running 0 tests [INFO] [stderr] Doc-tests laminar [INFO] [stdout] [INFO] [stdout] test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] running 0 tests [INFO] [stdout] [INFO] [stdout] test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out [INFO] [stdout] [INFO] [stderr] warning: unknown attribute `no-run`. Did you mean `no_run`? [INFO] [stderr] --> /opt/rustwide/workdir/src/infrastructure/arranging/ordering.rs:1:1 [INFO] [stderr] | [INFO] [stderr] 1 | / //! Module with logic for arranging items in-order on multiple streams. [INFO] [stderr] 2 | | //! [INFO] [stderr] 3 | | //! _"Order is the process of putting something in a particular order."_ [INFO] [stderr] 4 | | //! [INFO] [stderr] ... | [INFO] [stderr] 71 | | //! # Remarks [INFO] [stderr] 72 | | //! - See [super-module](../index.html) description for more details. [INFO] [stderr] | |_____________________________________________________________________^ [INFO] [stderr] | [INFO] [stderr] = note: `#[warn(invalid_codeblock_attributes)]` on by default [INFO] [stderr] = help: the code block will either not be tested if not marked as a rust one or will be run (which you might not want) [INFO] [stderr] [INFO] [stderr] warning: 1 warning emitted [INFO] [stderr] [INFO] [stdout] [INFO] [stdout] running 1 test [INFO] [stdout] test src/infrastructure/arranging/ordering.rs - infrastructure::arranging::ordering::OrderingStream::iter_mut (line 201) ... ignored [INFO] [stdout] [INFO] [stdout] test result: ok. 0 passed; 0 failed; 1 ignored; 0 measured; 0 filtered out [INFO] [stdout] [INFO] running `Command { std: "docker" "inspect" "fe8bf9011165d709afd3de9ed801bf9c7f4ce1883834b978dbb98f3bf0559015", kill_on_drop: false }` [INFO] running `Command { std: "docker" "rm" "-f" "fe8bf9011165d709afd3de9ed801bf9c7f4ce1883834b978dbb98f3bf0559015", kill_on_drop: false }` [INFO] [stdout] fe8bf9011165d709afd3de9ed801bf9c7f4ce1883834b978dbb98f3bf0559015