Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 11 Mar 2022 10:35:30 +0000 (GMT)
From:      jenkins-admin@FreeBSD.org
To:        bapt@FreeBSD.org, dev-ci@FreeBSD.org
Cc:        jenkins-admin@FreeBSD.org
Subject:   FreeBSD-main-amd64-test - Build #20838 - Still Unstable
Message-ID:  <1724718801.10955.1646994930925@jenkins.ci.freebsd.org>
In-Reply-To: <105371453.10951.1646990342080@jenkins.ci.freebsd.org>
References:  <105371453.10951.1646990342080@jenkins.ci.freebsd.org>

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

FreeBSD-main-amd64-test - Build #20838 (2eee44bd5ebcb88bf304215be1b0c68b6802a924) - Still Unstable

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

2eee44bd5ebcb88bf304215be1b0c68b6802a924 by bapt:
df: do not report a 100% full inode usage on fs without inodes



The failed test cases:

1 tests failed.
FAILED:  sys.netpfil.pf.pfsync.basic_defer

Error Message:
Failed to set PF rules in two
------=_Part_10954_205079386.1646994930419--



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