FreeBSD-main-amd64-test - Build #25232 - Still Unstable

From: <jenkins-admin_at_FreeBSD.org>
Date: Thu, 09 May 2024 16:03:09 UTC
FreeBSD-main-amd64-test - Build #25232 (f1612e7087d7c3df766ff0bf58c48d02fb0e2f6d) - Still Unstable

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

ebcfab998e631fa7e29e1c0694868d745fc085ee by jhb:
nvme: Explicitly align struct nvme_command on an 8 byte boundary

1116e8b95c601ddaac2feb4ab0904f77801a520f by adrian:
net80211: add a new field specifically for announcing specific ciphers

491938d7435f6a1ee7b6e5a669a72e4c12bd7d2b by adrian:
wpa: Remove the now not-needed local logic to hard-code cipher support

e9961ea164968bf2bdab210eab69201b4bf2cb37 by adrian:
net80211: add driver / crypto methods to set the hardware / software

c2a005a0a97d98472d81c5c9606e5d6e546dd40a by adrian:
net80211: add new ciphers and RSN flags

ce7756fdca1f0a89a74bc406cd3d3ac1d1be1ffb by cperciva:
release: make dependencies, not recursive make

ee72bc1d1ff8aa8704d5861a10ea3514154ff74d by royger:
xen/debug: remove usage of sbuf_{clear,finish}() on drained sbuf

f1612e7087d7c3df766ff0bf58c48d02fb0e2f6d by kp:
libpfctl: fix file descriptor leak



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)