Repository files (latest commit first)

Filename	Latest commit message	Latest commit date
Paolo Abeni a0ac20fd53 selftests: net: avoid just another constant wait ... [ Upstream commit 691bb4e49c98a47bc643dd808453136ce78b15b4 ] Using hard-coded constant timeout to wait for some expected event is deemed to fail sooner or later, especially in slow env. Our CI has spotted another of such race: # TEST: ipv6: cleanup of cached exceptions - nexthop objects [FAIL] # can't delete veth device in a timely manner, PMTU dst likely leaked Replace the crude sleep with a loop looking for the expected condition at low interval for a much longer range. Fixes: b3cc4f8a8a ("selftests: pmtu: add explicit tests for PMTU exceptions cleanup") Signed-off-by: Paolo Abeni <pabeni@redhat.com> Reviewed-by: David Ahern <dsahern@kernel.org> Link: https://lore.kernel.org/r/fd5c745e9bb665b724473af6a9373a8c2a62b247.1706812005.git.pabeni@redhat.com Signed-off-by: Jakub Kicinski <kuba@kernel.org> Signed-off-by: Sasha Levin <sashal@kernel.org>		2024-02-23 08:25:06 +01:00
..
fault-injection
ktest	ktest.pl: Add RUN_TIMEOUT option with default unlimited	2023-03-11 16:44:05 +01:00
nvdimm
radix-tree	radix tree test suite: fix incorrect allocation size for pthreads	2023-08-16 18:19:23 +02:00
scatterlist
selftests	selftests: net: avoid just another constant wait	2024-02-23 08:25:06 +01:00
vsock