go-ethereum/p2p
Charles Dusek e1fe4a1a98
p2p/discover: fix flaky TestUDPv5_findnodeHandling (#34109)
Fixes #34108

The UDPv5 test harness (`newUDPV5Test`) uses the default `PingInterval`
of 3 seconds. When tests like `TestUDPv5_findnodeHandling` insert nodes
into the routing table via `fillTable`, the table's revalidation loop
may schedule PING packets for those nodes. Under the race detector or on
slow CI runners, the test runs long enough for revalidation to fire,
causing background pings to be written to the test pipe. The `close()`
method then finds these as unmatched packets and fails.

The fix sets `PingInterval` to a very large value in the test harness so
revalidation never fires during tests.

Verified locally: 100 iterations with `-race -count=100` pass reliably,
where previously the test would fail within ~50 iterations.
2026-04-14 09:43:44 +02:00
..
discover p2p/discover: fix flaky TestUDPv5_findnodeHandling (#34109) 2026-04-14 09:43:44 +02:00
dnsdisc crypto/keccak: vendor in golang.org/x/crypto/sha3 (#33323) 2026-02-03 14:55:27 -07:00
enode crypto/keccak: vendor in golang.org/x/crypto/sha3 (#33323) 2026-02-03 14:55:27 -07:00
enr
msgrate
nat p2p/nat: fix err shadowing in UPnP addAnyPortMapping (#33355) 2025-12-08 15:02:24 +01:00
netutil
pipes
rlpx crypto/keccak: vendor in golang.org/x/crypto/sha3 (#33323) 2026-02-03 14:55:27 -07:00
tracker p2p/tracker: fix crash in clean when tracker is stopped (#33940) 2026-03-03 12:54:24 +01:00
config.go
config_toml.go
dial.go p2p: track in-progress inbound node IDs (#33198) 2026-03-20 05:52:15 +01:00
dial_test.go p2p: track in-progress inbound node IDs (#33198) 2026-03-20 05:52:15 +01:00
message.go
message_test.go
metrics.go
peer.go
peer_error.go
peer_test.go
protocol.go
server.go p2p: track in-progress inbound node IDs (#33198) 2026-03-20 05:52:15 +01:00
server_nat.go
server_nat_test.go
server_test.go
transport.go
transport_test.go
util.go
util_test.go