Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 15 Mar 2024 08:24:56 +0000 (GMT)
From:      jenkins-admin@FreeBSD.org
To:        kevans@FreeBSD.org, dev-ci@FreeBSD.org
Cc:        jenkins-admin@FreeBSD.org
Subject:   FreeBSD-main-amd64-test - Build #24942 - Still Unstable
Message-ID:  <220135729.3997.1710491096780@jenkins.ci.freebsd.org>
In-Reply-To: <1270087333.3989.1710485708892@jenkins.ci.freebsd.org>
References:  <1270087333.3989.1710485708892@jenkins.ci.freebsd.org>

next in thread | previous in thread | raw e-mail | index | archive | help
------=_Part_3996_1895325349.1710491096562
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit

FreeBSD-main-amd64-test - Build #24942 (3705d679a6344c957cae7a1b6372a8bfb8c44f0e) - Still Unstable

Build information: https://ci.FreeBSD.org/job/FreeBSD-main-amd64-test/24942/
Full change log: https://ci.FreeBSD.org/job/FreeBSD-main-amd64-test/24942/changes
Full build log: https://ci.FreeBSD.org/job/FreeBSD-main-amd64-test/24942/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)

3705d679a6344c957cae7a1b6372a8bfb8c44f0e by kevans:
if_wg: use proper barriers around pkt->p_state



The failed test cases:

3 tests failed.
FAILED:  sys.netpfil.common.dummynet.pf_queue

Error Message:
We failed prioritisation 1 times

FAILED:  sys.fs.tmpfs.times_test.empty

Error Message:
Test case was expecting a failure but none were raised

FAILED:  cddl.usr.sbin.zfsd.zfsd_unittest.main

Error Message:
Received signal 6
------=_Part_3996_1895325349.1710491096562--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?220135729.3997.1710491096780>