Date: Tue, 19 Apr 2022 03:38:02 +0000 (GMT) From: jenkins-admin@FreeBSD.org To: asomers@FreeBSD.org, dev-ci@FreeBSD.org Cc: jenkins-admin@FreeBSD.org Subject: FreeBSD-main-amd64-test - Build #21174 - Still Unstable Message-ID: <379001706.3399.1650339483048@jenkins.ci.freebsd.org> In-Reply-To: <1281445388.3391.1650335315168@jenkins.ci.freebsd.org> References: <1281445388.3391.1650335315168@jenkins.ci.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
------=_Part_3398_772183987.1650339482540 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit FreeBSD-main-amd64-test - Build #21174 (3a1b3c6a1e68063330e897a5a5c94518edae4a3b) - Still Unstable Build information: https://ci.FreeBSD.org/job/FreeBSD-main-amd64-test/21174/ Full change log: https://ci.FreeBSD.org/job/FreeBSD-main-amd64-test/21174/changes Full build log: https://ci.FreeBSD.org/job/FreeBSD-main-amd64-test/21174/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) 3a1b3c6a1e68063330e897a5a5c94518edae4a3b by asomers: fusefs: correctly handle servers that report too much data written The failed test cases: 2 tests failed. FAILED: sys.kern.ptrace_test.ptrace__follow_fork_parent_detached_unrelated_debugger Error Message: /usr/src/tests/sys/kern/ptrace_test.c:603: WIFSTOPPED(status) not met FAILED: sys.kern.ptrace_test.ptrace__follow_fork_both_attached_unrelated_debugger Error Message: /usr/src/tests/sys/kern/ptrace_test.c:603: WIFSTOPPED(status) not met ------=_Part_3398_772183987.1650339482540--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?379001706.3399.1650339483048>