Page MenuHomeFreeBSD

tests/pf/route_to: check_random: rely on test timeout to fail
ClosedPublic

Authored by siva on Jun 3 2026, 3:35 PM.
Tags
None
Referenced Files
F170488841: D57408.id179134.diff
Sat, Sep 5, 1:49 AM
Unknown Object (File)
Thu, Sep 3, 7:02 PM
Unknown Object (File)
Wed, Sep 2, 5:35 PM
Unknown Object (File)
Tue, Sep 1, 7:04 PM
Unknown Object (File)
Mon, Aug 31, 2:58 PM
Unknown Object (File)
Sun, Aug 30, 7:13 PM
Unknown Object (File)
Sat, Aug 29, 6:08 AM
Unknown Object (File)
Fri, Aug 28, 9:24 PM

Details

Summary

This test is known to be flaky if 10 attempts happens to be
not enough for the test to pass. Usually, this test passes in ~4-6 attempts.
See https://ci.freebsd.org/job/FreeBSD-main-amd64-test/28664/testReport/junit/sys.netpfil.pf/route_to/random_table/

Rely on the timeout (default 5 mins) to catch a failure here, rather than just 10
attempts. It's very unlikely that 5 mins worth of attempts still isn't enough.

For a history of flakiness, see
https://ci.freebsd.org/job/FreeBSD-main-amd64-test/lastSuccessfulBuild/testReport/junit/sys.netpfil.pf/route_to/random_table/history/

PR: 289477

Diff Detail

Repository
rG FreeBSD src repository
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

siva requested review of this revision.Jun 3 2026, 3:35 PM
This revision is now accepted and ready to land.Jun 5 2026, 12:10 PM
tests/sys/netpfil/pf/route_to.sh
50–52

Could you please add a comment to note that this infinite loop is intentional? It doesn't have to be overly verbose -- just to ensure that someone doesn't drop the change by accident.
Also, should this have a short sleep to avoid burning a ton of CPU in this loop?

Added comment around infinite loop and updated other test related comments.

This revision now requires review to proceed.Jun 15 2026, 5:18 PM
This revision was not accepted when it landed; it landed in state Needs Review.Jun 17 2026, 4:53 PM
This revision was automatically updated to reflect the committed changes.