Date: Fri, 8 Apr 2022 02:25:31 +0000 (GMT) From: jenkins-admin@FreeBSD.org To: alfredo@FreeBSD.org, dev-ci@FreeBSD.org Cc: jenkins-admin@FreeBSD.org Subject: FreeBSD-main-amd64-test - Build #21086 - Still Unstable Message-ID: <983250737.2167.1649384732453@jenkins.ci.freebsd.org> In-Reply-To: <1761872907.2153.1649375668259@jenkins.ci.freebsd.org> References: <1761872907.2153.1649375668259@jenkins.ci.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
------=_Part_2166_672499448.1649384731986 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit FreeBSD-main-amd64-test - Build #21086 (0b1b30d66450b20bf18fb4ab39bc6d4f5a6a28fe) - Still Unstable Build information: https://ci.FreeBSD.org/job/FreeBSD-main-amd64-test/21086/ Full change log: https://ci.FreeBSD.org/job/FreeBSD-main-amd64-test/21086/changes Full build log: https://ci.FreeBSD.org/job/FreeBSD-main-amd64-test/21086/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) 0b1b30d66450b20bf18fb4ab39bc6d4f5a6a28fe by alfredo: nfs: do not panic on bootpc_init when no interfaces are found The failed test cases: 2 tests failed. FAILED: sys.netpfil.pf.ether.anchor Error Message: Failed to set PF rules in alcatraz FAILED: sys.netpfil.pf.table.pr251414 Error Message: Failed to set PF rules in alcatraz ------=_Part_2166_672499448.1649384731986--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?983250737.2167.1649384732453>