Page MenuHomeFreeBSD

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

Authored by siva on Wed, Jun 3, 3:35 PM.
Tags
None
Referenced Files
F159885707: D57408.id179810.diff
Fri, Jun 19, 3:02 AM
Unknown Object (File)
Thu, Jun 18, 4:27 AM
Unknown Object (File)
Thu, Jun 18, 4:24 AM
Unknown Object (File)
Wed, Jun 17, 3:26 PM
Unknown Object (File)
Tue, Jun 16, 5:47 PM
Unknown Object (File)
Tue, Jun 16, 4:13 PM
Unknown Object (File)
Sun, Jun 14, 6:32 PM
Unknown Object (File)
Sat, Jun 13, 5:08 AM

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.Wed, Jun 3, 3:35 PM
This revision is now accepted and ready to land.Fri, Jun 5, 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.Mon, Jun 15, 5:18 PM
This revision was not accepted when it landed; it landed in state Needs Review.Wed, Jun 17, 4:53 PM
This revision was automatically updated to reflect the committed changes.