mirror of
git://git.yoctoproject.org/linux-yocto.git
synced 2025-08-21 16:31:14 +02:00
![]() Some packetdrill tests are flaky in debug mode. As discussed, increase
tolerance.
We have been doing this for debug builds outside ksft too.
Previous setting was 10000. A manual 50 runs in virtme-ng showed two
failures that needed 12000. To be on the safe side, Increase to 14000.
Link: https://lore.kernel.org/netdev/Zuhhe4-MQHd3EkfN@mini-arch/
Fixes:
|
||
---|---|---|
.. | ||
config | ||
defaults.sh | ||
ksft_runner.sh | ||
Makefile | ||
set_sysctls.py | ||
tcp_inq_client.pkt | ||
tcp_inq_server.pkt | ||
tcp_md5_md5-only-on-client-ack.pkt | ||
tcp_slow_start_slow-start-ack-per-1pkt.pkt | ||
tcp_slow_start_slow-start-ack-per-2pkt-send-5pkt.pkt | ||
tcp_slow_start_slow-start-ack-per-2pkt-send-6pkt.pkt | ||
tcp_slow_start_slow-start-ack-per-2pkt.pkt | ||
tcp_slow_start_slow-start-ack-per-4pkt.pkt | ||
tcp_slow_start_slow-start-after-idle.pkt | ||
tcp_slow_start_slow-start-after-win-update.pkt | ||
tcp_slow_start_slow-start-app-limited-9-packets-out.pkt | ||
tcp_slow_start_slow-start-app-limited.pkt | ||
tcp_slow_start_slow-start-fq-ack-per-2pkt.pkt | ||
tcp_zerocopy_basic.pkt | ||
tcp_zerocopy_batch.pkt | ||
tcp_zerocopy_client.pkt | ||
tcp_zerocopy_closed.pkt | ||
tcp_zerocopy_epoll_edge.pkt | ||
tcp_zerocopy_epoll_exclusive.pkt | ||
tcp_zerocopy_epoll_oneshot.pkt | ||
tcp_zerocopy_fastopen-client.pkt | ||
tcp_zerocopy_fastopen-server.pkt | ||
tcp_zerocopy_maxfrags.pkt | ||
tcp_zerocopy_small.pkt |