Date: Tue, 23 Jun 2026 12:17:26 +0000 (GMT) From: jenkins-admin@FreeBSD.org To: pouria@FreeBSD.org, dev-ci@FreeBSD.org Cc: jenkins-admin@FreeBSD.org Subject: FreeBSD-main-amd64-test - Build #28863 - Still Unstable Message-ID: <156358928.63.1782217046763@jenkins.ci.freebsd.org> In-Reply-To: <1018433401.57.1782209103408@jenkins.ci.freebsd.org>
index | next in thread | previous in thread | raw e-mail
FreeBSD-main-amd64-test - Build #28863 (2e6b22abf44d99b84abf17fe25ca2e8f89716c04) - Still Unstable Build information: https://ci.FreeBSD.org/job/FreeBSD-main-amd64-test/28863/ Full change log: https://ci.FreeBSD.org/job/FreeBSD-main-amd64-test/28863/changes Full build log: https://ci.FreeBSD.org/job/FreeBSD-main-amd64-test/28863/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) 2e6b22abf44d99b84abf17fe25ca2e8f89716c04 by pouria: ipfw/nat64: Fix type confusion panic when using wrong NAT64 instance The failed test cases: 1 tests failed. FAILED: sys.kern.aslr.aslr_setuid Error Message: /usr/src/tests/sys/kern/aslr.c:122: failed to find /sbin/ping text segmenthome | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?156358928.63.1782217046763>