Date: Mon, 14 Mar 2022 09:44:13 +0000 (GMT) From: jenkins-admin@FreeBSD.org To: wma@FreeBSD.org, dev-ci@FreeBSD.org Cc: jenkins-admin@FreeBSD.org Subject: FreeBSD-main-amd64-test - Build #20863 - Still Unstable Message-ID: <625207654.11177.1647251053552@jenkins.ci.freebsd.org> In-Reply-To: <581719510.11171.1647246984152@jenkins.ci.freebsd.org> References: <581719510.11171.1647246984152@jenkins.ci.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
------=_Part_11176_1574819606.1647251053041 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit FreeBSD-main-amd64-test - Build #20863 (25bcd81b8d12468e28e438f58dd58e7c5ea8f8db) - Still Unstable Build information: https://ci.FreeBSD.org/job/FreeBSD-main-amd64-test/20863/ Full change log: https://ci.FreeBSD.org/job/FreeBSD-main-amd64-test/20863/changes Full build log: https://ci.FreeBSD.org/job/FreeBSD-main-amd64-test/20863/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) 25bcd81b8d12468e28e438f58dd58e7c5ea8f8db by wma: armv6/legacy: optimize cpu_getcount performance The failed test cases: 2 tests failed. FAILED: sys.netpfil.pf.pass_block.v6 Error Message: Failed to set PF rules in alcatraz FAILED: sys.netpfil.pf.set_skip.pr255852 Error Message: Failed to set PF rules in alcatraz ------=_Part_11176_1574819606.1647251053041--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?625207654.11177.1647251053552>