Date: Fri, 31 Mar 2023 13:49:40 +0000 (GMT) From: jenkins-admin@FreeBSD.org To: andrew@FreeBSD.org, bz@FreeBSD.org, dev-ci@FreeBSD.org Cc: jenkins-admin@FreeBSD.org Subject: FreeBSD-main-amd64-test - Build #23264 - Still Unstable Message-ID: <1463939821.1391.1680270581407@jenkins.ci.freebsd.org> In-Reply-To: <1522485747.1385.1680255232749@jenkins.ci.freebsd.org> References: <1522485747.1385.1680255232749@jenkins.ci.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
------=_Part_1390_319930601.1680270580983 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit FreeBSD-main-amd64-test - Build #23264 (3a0cc6fe61ea29334c17dfb71bf24ba9e604ab4c) - Still Unstable Build information: https://ci.FreeBSD.org/job/FreeBSD-main-amd64-test/23264/ Full change log: https://ci.FreeBSD.org/job/FreeBSD-main-amd64-test/23264/changes Full build log: https://ci.FreeBSD.org/job/FreeBSD-main-amd64-test/23264/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) 3f0083c4e30ab41fad1e93e4138767df42dbdf20 by bz: LinuxKPI: 802.11: use ic_printf more consistently 3a0cc6fe61ea29334c17dfb71bf24ba9e604ab4c by andrew: Handle the arm64 unknown exception separately The failed test cases: 1 tests failed. FAILED: sbin.ping.test_ping.py.TestPing::test_pinger[_3_1_verbose_false] Error Message: /usr/tests/sbin/ping/test_ping.py:1309: AssertionError ------=_Part_1390_319930601.1680270580983--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1463939821.1391.1680270581407>