FreeBSD-stable-15-amd64-test - Build #843 - Still Unstable

From: <jenkins-admin_at_FreeBSD.org>
Date: Sat, 13 Jun 2026 04:52:20 UTC
FreeBSD-stable-15-amd64-test - Build #843 (669642faa3942906438cd55b44921578fd3db2b4) - Still Unstable

Build information: https://ci.FreeBSD.org/job/FreeBSD-stable-15-amd64-test/843/
Full change log: https://ci.FreeBSD.org/job/FreeBSD-stable-15-amd64-test/843/changes
Full build log: https://ci.FreeBSD.org/job/FreeBSD-stable-15-amd64-test/843/console

Status explanation:
"Unstable" - some tests are suspected being broken by the following changes
"Still Unstable" - the failing test cases have not been fixed by these
                   following changes and this is a notification to note that
                   these changes have not been fully tested by the CI system

Change summaries:
(Those commits are likely but not certainly responsible)

43702cfc0ccbd9b357243aedcf18e19d94a64ef9 by kib:
ntsync(4)

1ee1bfed821bec588b8bbaf04e214079ed5c3f54 by kib:
ntsync: install headers for userspace consumption

3118bdf37db67679a0017b7c2b0a32a142c43d95 by kib:
ntsync: add kinfo reporting

57c8cccbfca60d1782f7303502b73b28bde2bc53 by kib:
linux_ntsync: linux compat shim for ntsync(9)

fff29fbbbd24055c680c3bf44ba3d045dcf9714e by kib:
bindat(2)/connectat(2): allow implicit EMPTYPATH for unix domain sockets

c1d9ae3f417f0ce576ec86f7b83c4de6992d3f8f by kib:
open.2: document O_PATH behavior for bindat/connectat

f6de9c63314fcaa33c3723e22dd6f685550069d6 by kib:
uipc_usrreq: revert addition of EMPTYPATH for bindat(2)

94c62907ac8018915ecb273d556e6851162b091e by kib:
connectat(2): do not enable EMPTYPATH for AT_FDCWD

f9a216c4fcc1766798e93e376bc4e23ea99e9ddf by kib:
renameat(2): when retrying, check for pending signals

f8fc6a086e559855243ef3d2ffda35e1ae0e7d71 by kib:
rename(2): do not allow to rename root vnode of the mounted filesystem

a4ceed16a79490b44cc1a8a1add5dabc0930279a by kib:
procctl(): do not allow the process to exit inside kern_procctl_single()

6b02fe2caa5cdd3b0ad012f7a0a47b0bd1bbb758 by kib:
kern_procctl: add get_reaper_or_p() helper

5cffd95d23ebea181b1f5fe7529382c8d39e26b9 by kib:
procctl(PROC_REAP_GETPIDS): re-validate reaper after relock of

093cc4194e6e88569bc25ecb73f6d887c5d69037 by kib:
imgact_elf: handle unaligned phdrs

b52346b34159eb364e52b87a6c3a5bc34d36d9e6 by kib:
exit1(9): do not deadlock if exit is called due to PT_SC_REMOTERQ

06dae2185fc249ef30f13c343cc7139f20739671 by kib:
proc: add tree ref count

eac751c461d89de2676cb98936a8cde9b3ad2beb by kib:
kern_fork: guard against NULL newproc on the failure path

53d691cacae602f96a80a656ec8f508b65ace81c by kib:
reap_kill_subtree_once: when proctree_lock is dropped, reaper might

b7280eba6324c203b5aeb87827ffcf7e9da7e467 by kib:
procstat binary: do not skip pid if either path or osrel sysctls failed

669642faa3942906438cd55b44921578fd3db2b4 by kib:
compat32 wait4/6(2): only copy out when there is a pid to report



The failed test cases:

2 tests failed.
FAILED:  sys.netpfil.pf.route_to.prefer_ipv6_nexthop_mixed_af_random_table_ipv4

Error Message:
Target 2001:db8:4202::42:4 not selected after 10 attempts!

FAILED:  sys.kern.aslr.aslr_setuid

Error Message:
/usr/src/tests/sys/kern/aslr.c:112: failed to find /sbin/ping text segment