[Bug 289477] sys/netpfil/pf/route_to:pr efer_ipv6_nexthop_mixed_af_random_table_ipv4 test fails intermittently in CI

From: <bugzilla-noreply_at_freebsd.org>
Date: Thu, 11 Sep 2025 20:11:16 UTC
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=289477

            Bug ID: 289477
           Summary: sys/netpfil/pf/route_to:prefer_ipv6_nexthop_mixed_af_r
                    andom_table_ipv4 test fails intermittently in CI
           Product: Base System
           Version: CURRENT
          Hardware: Any
                OS: Any
            Status: New
          Keywords: regression
          Severity: Affects Only Me
          Priority: ---
         Component: tests
          Assignee: ks@FreeBSD.org
          Reporter: me@svmhdvn.name
                CC: kp@freebsd.org, testing@FreeBSD.org

Created attachment 263728
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=263728&action=edit
kyua test report

The 'sys/netpfil/pf/route_to:prefer_ipv6_nexthop_mixed_af_random_table_ipv4'
testcase fails intermittently in CI:


===> sys/netpfil/pf/route_to:prefer_ipv6_nexthop_mixed_af_random_table_ipv4
Result:     failed: Target 2001:db8:4202::42:4 not selected after 10 attempts!


I have reproduced this error using Bricoler with 100 runs for good measure and
attached the failing test report in this bug:

$ bricoler run freebsd-src-regression-suite --param freebsd-src:url=/usr/src
--param freebsd-src:branch= --param
freebsd-src-regression-suite:hypervisor=bhyve --param
freebsd-src-regression-suite:memory=4096 --param
freebsd-src-regression-suite:ncpus=2 --param
freebsd-src-regression-suite:parallelism=1 --param
freebsd-src-regression-suite:count=100 --param
freebsd-src-regression-suite:tests='sys/netpfil/pf/route_to:prefer_ipv6_nexthop_mixed_af_random_table_ipv4'

@ks, since you made the last significant edit to the tests in
https://cgit.freebsd.org/src/commit/?id=65c318630123fcf2b6f491bf4d02a5cad3031d20
(pf: Add prefer-ipv6-nexthop option for route-to pools), please triage as
necessary.

-- 
You are receiving this mail because:
You are on the CC list for the bug.