FreeBSD-main-amd64-test - Build #25236 - Still unstable

From: <jenkins-admin_at_FreeBSD.org>
Date: Mon, 13 May 2024 17:03:09 UTC
FreeBSD-main-amd64-test - Build #25236 (050555e129789fa2e20eba565f1320936b3d66e4) - Still unstable

Build information: https://ci.FreeBSD.org/job/FreeBSD-main-amd64-test/25236/
Full change log: https://ci.FreeBSD.org/job/FreeBSD-main-amd64-test/25236/changes
Full build log: https://ci.FreeBSD.org/job/FreeBSD-main-amd64-test/25236/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)

47535ba3d35eda44d1eb961551173a9dadef17fa by fernape:
bsdinstall: Remove unused variables in fetchmissingdists

94b09d388b81eb724769e506cdf0f51bba9b73fb by alc:
arm64: map kernel using large pages when page size is 16K

be04fec42638f30f50b5b55fd8e3634c0fb89928 by kevans:
Import _FORTIFY_SOURCE implementation from NetBSD

e55512504d0178983978d64d67eed1cc85826523 by kevans:
Prepare the system for _FORTIFY_SOURCE

9bfd3b4076a7b0dfd27ab22318e5113dc84fea28 by kevans:
Add a build knob for _FORTIFY_SOURCE

421025a274fb5759b3ecc8bdb30b24db830b45ae by gbe:
access.2: Mention that lstat(2) should be used for symbolic links

59a6666ec91d71f97aaae5195bbfafd9d422db2e by kp:
if_ovpn: cope with loops

f3eeeb959c9b00c89a2e1ff009c78162eb398656 by des:
expand: Fix markup for the `-t` option.

050555e129789fa2e20eba565f1320936b3d66e4 by oshogbo:
syscalls.master: allow vfork(2) in capsicum(4) capability mode



The failed test cases:

2 tests failed.
FAILED:  sys.kern.unix_seqpacket_test.random_eor_and_waitall

Error Message:
/usr/src/tests/sys/kern/unix_seqpacket_test.c:1182: send(params->sock, &params->sendbuf[off], len, flags) == len not met

FAILED:  sys.netinet6.divert.ipdivert_ip6_output_remote_success

Error Message:
1 != 0 (1 != 0)