Date: Fri, 11 Mar 2022 11:46:58 +0000 (GMT) From: jenkins-admin@FreeBSD.org To: hselasky@FreeBSD.org, dev-ci@FreeBSD.org Cc: jenkins-admin@FreeBSD.org Subject: FreeBSD-main-amd64-test - Build #20839 - Still Unstable Message-ID: <1843993577.10961.1646999219256@jenkins.ci.freebsd.org> In-Reply-To: <1724718801.10955.1646994930925@jenkins.ci.freebsd.org> References: <1724718801.10955.1646994930925@jenkins.ci.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
------=_Part_10960_1527132466.1646999218704 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit FreeBSD-main-amd64-test - Build #20839 (c5f549c1e0c9aa1764e87d55f183053c1545b1fc) - Still Unstable Build information: https://ci.FreeBSD.org/job/FreeBSD-main-amd64-test/20839/ Full change log: https://ci.FreeBSD.org/job/FreeBSD-main-amd64-test/20839/changes Full build log: https://ci.FreeBSD.org/job/FreeBSD-main-amd64-test/20839/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) c5f549c1e0c9aa1764e87d55f183053c1545b1fc by hselasky: newfs(8): Fix a bug in initialization of sblock.fs_maxbsize . The failed test cases: 3 tests failed. FAILED: sys.netpfil.pf.ether.anchor Error Message: Failed to set PF rules in alcatraz FAILED: sys.netpfil.pf.ether.mac Error Message: Failed to set PF rules in alcatraz FAILED: sys.netpfil.pf.pfsync.basic Error Message: Failed to set PF rules in two ------=_Part_10960_1527132466.1646999218704--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1843993577.10961.1646999219256>