Date: Mon, 7 Feb 2022 14:57:00 +0000 (GMT) From: jenkins-admin@FreeBSD.org To: andrew@FreeBSD.org, dev-ci@FreeBSD.org Cc: jenkins-admin@FreeBSD.org Subject: FreeBSD-main-amd64-test - Build #20599 - Still Unstable Message-ID: <125148056.8687.1644245820720@jenkins.ci.freebsd.org> In-Reply-To: <464869885.8681.1644241859906@jenkins.ci.freebsd.org> References: <464869885.8681.1644241859906@jenkins.ci.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
------=_Part_8686_1035621915.1644245820090 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit FreeBSD-main-amd64-test - Build #20599 (67dc576bae6e624ae46962ad187e0e31fece6688) - Still Unstable Build information: https://ci.FreeBSD.org/job/FreeBSD-main-amd64-test/20599/ Full change log: https://ci.FreeBSD.org/job/FreeBSD-main-amd64-test/20599/changes Full build log: https://ci.FreeBSD.org/job/FreeBSD-main-amd64-test/20599/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) 67dc576bae6e624ae46962ad187e0e31fece6688 by andrew: Fix the signal code on 32-bit breakpoints on arm64 The failed test cases: 2 tests failed. FAILED: sys.netpfil.common.dummynet.ipfw_queue Error Message: We failed prioritisation 1 times FAILED: sys.geom.class.multipath.failloop.failloop Error Message: dtrace didn't execute successfully ------=_Part_8686_1035621915.1644245820090--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?125148056.8687.1644245820720>