Date: Fri, 18 Mar 2022 01:19:46 +0000 (GMT) From: jenkins-admin@FreeBSD.org To: rew@FreeBSD.org, kp@FreeBSD.org, markj@FreeBSD.org, dev-ci@FreeBSD.org Cc: jenkins-admin@FreeBSD.org Subject: FreeBSD-main-amd64-test - Build #20898 - Unstable Message-ID: <2084198362.11515.1647566386933@jenkins.ci.freebsd.org>
next in thread | raw e-mail | index | archive | help
------=_Part_11514_151229047.1647566386263 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit FreeBSD-main-amd64-test - Build #20898 (d234b011a8f1cf90acbda2e3cd166459736c7ed2) - Unstable Build information: https://ci.FreeBSD.org/job/FreeBSD-main-amd64-test/20898/ Full change log: https://ci.FreeBSD.org/job/FreeBSD-main-amd64-test/20898/changes Full build log: https://ci.FreeBSD.org/job/FreeBSD-main-amd64-test/20898/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) c0b98fe16f253d6b5693adeb38cdb78cadb5f58d by markj: fusefs: Initialize a pad word in the mknod message 8772a9117b27f551f6fbaae9413acaa30d99f934 by rew: mount.8: mention that the snapshot option is exclusive d234b011a8f1cf90acbda2e3cd166459736c7ed2 by kp: netinet tests: only log critical errors from scapy The failed test cases: 3 tests failed. FAILED: sys.netpfil.pf.ether.mac Error Message: Failed to set PF rules in alcatraz FAILED: sys.netpfil.pf.pfsync.basic_defer Error Message: Failed to set PF rules in two FAILED: sys.netpfil.pf.table.pr251414 Error Message: Failed to set PF rules in alcatraz ------=_Part_11514_151229047.1647566386263--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?2084198362.11515.1647566386933>