Date: Fri, 4 Mar 2022 13:57:52 +0000 (GMT) From: jenkins-admin@FreeBSD.org To: pho@FreeBSD.org, dev-ci@FreeBSD.org Cc: jenkins-admin@FreeBSD.org Subject: FreeBSD-main-amd64-test - Build #20784 - Still Unstable Message-ID: <51761940.10395.1646402273677@jenkins.ci.freebsd.org> In-Reply-To: <342510030.10389.1646378321522@jenkins.ci.freebsd.org> References: <342510030.10389.1646378321522@jenkins.ci.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
------=_Part_10394_209536305.1646402272864 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit FreeBSD-main-amd64-test - Build #20784 (205117128771033174b18d79a14d3c6f7dc195cc) - Still Unstable Build information: https://ci.FreeBSD.org/job/FreeBSD-main-amd64-test/20784/ Full change log: https://ci.FreeBSD.org/job/FreeBSD-main-amd64-test/20784/changes Full build log: https://ci.FreeBSD.org/job/FreeBSD-main-amd64-test/20784/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) 205117128771033174b18d79a14d3c6f7dc195cc by pho: stress2: Added a new test scenario checing for a long fsck_ffs runtime The failed test cases: 1 tests failed. FAILED: sys.file.closefrom_test.main Error Message: TAP test program yielded invalid data: Load of '/tmp/kyua.2Lsz9P/1289/stdout.txt' failed: Reported plan differs from actual executed tests ------=_Part_10394_209536305.1646402272864--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?51761940.10395.1646402273677>