FreeBSD-main-amd64-test - Build #24377 - Failure

From: <jenkins-admin_at_FreeBSD.org>
Date: Tue, 14 Nov 2023 03:10:49 UTC
FreeBSD-main-amd64-test - Build #24377 (0e8044064716fa7cf4fd9a98016f6e8c8f108333) - Failure

Build information: https://ci.FreeBSD.org/job/FreeBSD-main-amd64-test/24377/
Full change log: https://ci.FreeBSD.org/job/FreeBSD-main-amd64-test/24377/changes
Full build log: https://ci.FreeBSD.org/job/FreeBSD-main-amd64-test/24377/console

Status explanation:
"Failure" - the build is suspected being broken by the following changes
"Still Failing" - the build has not been fixed by the 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)

3a88fe13354325b9f56f07927e654de4f5398707 by cy:
sqlite3: Vendor import of sqlite3 3.44.0

b9c0003f0fa39ead4bb3953b9118ae6f08e560f8 by markj:
arm64: Initialize x18 for APs earlier during boot

c6d7be214811c315d234d64c6cbaa92d4f55d2c1 by christos:
tty: properly check character position when handling IUTF8 backspaces

49025a1109ac5f8088d21788413f843dd730e217 by imp:
_bus.h: Use standard licnese text

0e8044064716fa7cf4fd9a98016f6e8c8f108333 by imp:
busdma: Add deferred time measurement to arm and powerpc



The end of the build log:

[...truncated 4.83 MB...]
epair0a: link state changed to UP
epair0b: link state changed to UP
epair0a: link state changed to DOWN
epair0b: link state changed to DOWN
passed  [0.166s]
sys/net/routing/test_rtsock_l3:rtm_del_v6_gu_ifa_hostroute_success  ->  epair0a: Ethernet address: 02:de:2a:01:42:0a
epair0b: Ethernet address: 02:de:2a:01:42:0b
epair0a: link state changed to UP
epair0b: link state changed to UP
epair0a: link state changed to DOWN
epair0b: link state changed to DOWN
passed  [0.172s]
sys/net/routing/test_rtsock_l3:rtm_del_v6_gu_ifa_prefixroute_success  ->  epair0a: Ethernet address: 02:be:59:57:cf:0a
epair0b: Ethernet address: 02:be:59:57:cf:0b
epair0a: link state changed to UP
epair0b: link state changed to UP
epair0a: link state changed to DOWN
epair0b: link state changed to DOWN
passed  [0.171s]
sys/net/routing/test_rtsock_l3:rtm_del_v6_gu_prefix_nogw_success  ->  epair0a: Ethernet address: 02:40:1d:5e:7b:0a
epair0b: Ethernet address: 02:40:1d:5e:7b:0b
epair0a: link state changed to UP
epair0b: link state changed to UP
epair0a: link state changed to DOWN
epair0b: link state changed to DOWN
passed  [0.166s]
sys/net/routing/test_rtsock_l3:rtm_get_v4_empty_dst_failure  ->  passed  [0.007s]
sys/net/routing/test_rtsock_l3:rtm_get_v4_exact_success  ->  epair0a: Ethernet address: 02:d3:86:84:08:0a
epair0b: Ethernet address: 02:d3:86:84:08:0b
epair0a: link state changed to UP
epair0b: link state changed to UP
epair0a: link state changed to DOWN
epair0b: link state changed to DOWN
passed  [0.173s]
sys/net/routing/test_rtsock_l3:rtm_get_v4_hostbits_success  ->  epair0a: Ethernet address: 02:0b:54:c3:28:0a
epair0b: Ethernet address: 02:0b:54:c3:28:0b
epair0a: link state changed to UP
epair0b: link state changed to UP
epair0a: link state changed to DOWN
epair0b: link state changed to DOWN
passed  [0.160s]
sys/net/routing/test_rtsock_l3:rtm_get_v4_lpm_success  ->  epair0a: Ethernet address: 02:1d:7c:ad:35:0a
epair0b: Ethernet address: 02:1d:7c:ad:35:0b
epair0a: link state changed to UP
epair0b: link state changed to UP
epair0a: link state changed to DOWN
epair0b: link state changed to DOWN
passed  [0.160s]
sys/net/routing/test_rtsock_lladdr:rtm_add_v4_gu_lle_success  ->  epair0a: Ethernet address: 02:22:46:98:48:0a
epair0b: Ethernet address: 02:22:46:98:48:0b
epair0a: link state changed to UP
epair0b: link state changed to UP
epair0a: link state changed to DOWN
epair0b: link state changed to DOWN
passed  [0.167s]
sys/net/routing/test_rtsock_lladdr:rtm_add_v6_gu_lle_success  ->  epair0a: Ethernet address: 02:5d:a5:f2:8e:0a
epair0b: Ethernet address: 02:5d:a5:f2:8e:0b
epair0a: link state changed to UP
epair0b: link state changed to UP
epair0a: link state changed to DOWN
epair0b: link state changed to DOWN
passed  [0.165s]
sys/net/routing/test_rtsock_lladdr:rtm_add_v6_ll_lle_success  ->  epair0a: Ethernet address: 02:cf:1d:a5:39:0a
epair0b: Ethernet address: 02:cf:1d:a5:39:0b
epair0a: link state changed to UP
epair0b: link state changed to UP
epair0a: link state changed to DOWN
epair0b: link state changed to DOWN
passed  [0.157s]
sys/net/routing/test_rtsock_lladdr:rtm_del_v4_gu_lle_success  ->  epair0a: Ethernet address: 02:fa:8c:4a:09:0a
epair0b: Ethernet address: 02:fa:8c:4a:09:0b
epair0a: link state changed to UP
epair0b: link state changed to UP
epair0a: link state changed to DOWN
epair0b: link state changed to DOWN
passed  [0.166s]
sys/net/routing/test_rtsock_lladdr:rtm_del_v6_gu_lle_success  ->  epair0a: Ethernet address: 02:28:8f:10:88:0a
epair0b: Ethernet address: 02:28:8f:10:88:0b
epair0a: link state changed to UP
epair0b: link state changed to UP
epair0a: link state changed to DOWN
epair0b: link state changed to DOWN
passed  [0.161s]
sys/net/routing/test_rtsock_lladdr:rtm_del_v6_ll_lle_success  ->  epair0a: Ethernet address: 02:fb:f3:c6:b5:0a
epair0b: Ethernet address: 02:fb:f3:c6:b5:0b
epair0a: link state changed to UP
epair0b: link state changed to UP
epair0a: link state changed to DOWN
epair0b: link state changed to DOWN
passed  [0.160s]
sys/net/routing/test_rtsock_multipath.py:TestRtmMultipath::test_rtm_multipath4[change_new_weight1]  ->  epair0a: Ethernet address: 02:48:61:91:c7:0a
epair0b: Ethernet address: 02:48:61:91:c7:0b
epair0a: link state changed to UP
epair0b: link state changed to UP
lo0: link state changed to UP
epair0a: link state changed to DOWN
epair0b: link state changed to DOWN
passed  [0.513s]
sys/net/routing/test_rtsock_multipath.py:TestRtmMultipath::test_rtm_multipath4[change_new_weight2]  ->  epair0a: Ethernet address: 02:d9:06:0a:33:0a
epair0b: Ethernet address: 02:d9:06:0a:33:0b
epair0a: link state changed to UP
epair0b: link state changed to UP
lo0: link state changed to UP
epair0a: link state changed to DOWN
epair0b: link state changed to DOWN
passed  [0.472s]
sys/net/routing/test_rtsock_multipath.py:TestRtmMultipath::test_rtm_multipath4[change_new_weight3]  ->  epair0a: Ethernet address: 02:63:02:eb:f4:0a
epair0b: Ethernet address: 02:63:02:eb:f4:0b
epair0a: link state changed to UP
epair0b: link state changed to UP
lo0: link state changed to UP
epair0a: link state changed to DOWN
epair0b: link state changed to DOWN
passed  [0.506s]
sys/net/routing/test_rtsock_multipath.py:TestRtmMultipath::test_rtm_multipath4[change_same_weight1]  ->  epair0a: Ethernet address: 02:36:98:d9:9a:0a
epair0b: Ethernet address: 02:36:98:d9:9a:0b
epair0a: link state changed to UP
epair0b: link state changed to UP
lo0: link state changed to UP
epair0a: link state changed to DOWN
epair0b: link state changed to DOWN
passed  [0.461s]
sys/net/routing/test_rtsock_multipath.py:TestRtmMultipath::test_rtm_multipath4[change_same_weight2]  ->  epair0a: Ethernet address: 02:80:d7:34:bf:0a
epair0b: Ethernet address: 02:80:d7:34:bf:0b
epair0a: link state changed to UP
epair0b: link state changed to UP
lo0: link state changed to UP
epair0a: link state changed to DOWN
epair0b: link state changed to DOWN
passed  [0.515s]
sys/net/routing/test_rtsock_multipath.py:TestRtmMultipath::test_rtm_multipath4[correctness1]  ->  epair0a: Ethernet address: 02:1d:b5:dc:23:0a
epair0b: Ethernet address: 02:1d:b5:dc:23:0b
epair0a: link state changed to UP
epair0b: link state changed to UP
lo0: link state changed to UP
*** /usr/src/contrib/kyua/utils/process/executor.cpp:822: Invariant check failed: PID 69890 already in all_exec_handles; not properly cleaned up or reused too fast
*** Fatal signal 6 received
*** Log file is /.kyua/logs/kyua.20231114-021457.log
*** Please report this problem to kyua-discuss@googlegroups.com detailing what you were doing before the crash happened; if possible, include the log file mentioned above
pid 758 (kyua), jid 0, uid 0: exited on signal 6 (core dumped)
Abort trap (core dumped)
+ rc=134
+ set -e
+ [ 134 -ne 0 ]
+ [ 134 -ne 1 ]
+ exit 134
+ tar cvf /dev/vtbd1 -C /meta .
a .
a ./disable-zfs-tests.sh
a ./run-kyua.sh
a ./disable-notyet-tests.sh
a ./run.sh
a ./disable-dtrace-tests.sh
a ./auto-shutdown
+ [ -f /meta/auto-shutdown ]
+ uname -p
+ shutdown -p now
Shutdown NOW!
shutdown: [pid 69915]
+ startmsg .
+ check_startmsgs
+ [ -n yes ]
+ checkyesno rc_startmsgs
+ eval '_value=$rc_startmsgs'
+ _value=YES
+ debug 'checkyesno: rc_startmsgs is set to YES.'
+ return 0
+ echo .
.
+ _return=0
+ umask 0022
+ [ 0 -ne 0 ]
+ return 0
+ _run_rc_postcmd
+ [ -n '' ]
+ return 0
+ return 0
2023-11-14T03:10:40.947235+00:00 - shutdown 69915 - - power-down by root: 

System shutdown time has arrived
Waiting (max 60 seconds) for system process `vnlru' to stop... done
Waiting (max 60 seconds) for system process `syncer' to stop... epair0a: link state changed to DOWN
epair0b: link state changed to DOWN

Syncing disks, vnodes remaining... 0 0 done
All buffers synced.
lock order reversal:
 1st 0xfffff800097fdaf0 devfs (devfs, lockmgr) @ /usr/src/sys/kern/vfs_mount.c:2254
 2nd 0xfffff800099e33f0 fdescfs (fdescfs, lockmgr) @ /usr/src/sys/kern/vfs_subr.c:3296
lock order devfs -> fdescfs attempted at:
#0 0xffffffff80bc32de at witness_checkorder+0xbbe
#1 0xffffffff80b1cc51 at lockmgr_lock_flags+0x181
#2 0xffffffff80c5f0b3 at _vn_lock+0x53
#3 0xffffffff80c4669d at vget_finish+0x4d
#4 0xffffffff82610262 at fdesc_root+0x22
#5 0xffffffff80c4773b at vflush+0x4b
#6 0xffffffff82610211 at fdesc_unmount+0x71
#7 0xffffffff80c3c385 at dounmount+0x7b5
#8 0xffffffff80c48e7a at vfs_unmountall+0x6a
#9 0xffffffff80c193cc at bufshutdown+0x30c
#10 0xffffffff80b4fae3 at kern_reboot+0x713
#11 0xffffffff80b4f379 at sys_reboot+0x3a9
#12 0xffffffff81051dab at amd64_syscall+0x84b
#13 0xffffffff81023b9b at fast_syscall_common+0xf8
pid 472 (devd), jid 0, uid 0: exited on signal 11 (no core dump - other error)
Uptime: 55m48s
acpi0: Powering system off
+ rc=0
+ echo 'bhyve return code = 0'
bhyve return code = 0
+ sudo /usr/sbin/bhyvectl '--vm=testvm-main-amd64-24377' --destroy
+ sh -ex freebsd-ci/scripts/test/extract-meta.sh
+ METAOUTDIR=meta-out
+ rm -fr meta-out
+ mkdir meta-out
+ tar xvf meta.tar -C meta-out
x ./
x ./disable-zfs-tests.sh
x ./run-kyua.sh
x ./disable-notyet-tests.sh
x ./run.sh
x ./disable-dtrace-tests.sh
x ./auto-shutdown
+ rm -f test-report.txt test-report.xml
+ mv 'meta-out/test-report.*' .
mv: rename meta-out/test-report.* to ./test-report.*: No such file or directory
+ report=test-report.xml
+ [ -e freebsd-ci/jobs/FreeBSD-main-amd64-test/xfail-list -a -e test-report.xml ]
+ rm -f disk-cam
+ jot 5
+ rm -f disk1
+ rm -f disk2
+ rm -f disk3
+ rm -f disk4
+ rm -f disk5
+ rm -f disk-test.img
[PostBuildScript] - [INFO] Executing post build scripts.
[FreeBSD-main-amd64-test] $ /bin/sh -xe /tmp/jenkins15721653664284590684.sh
+ ./freebsd-ci/artifact/post-link.py
Post link: {'job_name': 'FreeBSD-main-amd64-test', 'commit': '0e8044064716fa7cf4fd9a98016f6e8c8f108333', 'branch': 'main', 'target': 'amd64', 'target_arch': 'amd64', 'link_type': 'latest_tested'}
"Link created: main/latest_tested/amd64/amd64 -> ../../0e8044064716fa7cf4fd9a98016f6e8c8f108333/amd64/amd64\n"
Recording test results
ERROR: Step ‘Publish JUnit test result report’ failed: No test report files were found. Configuration error?
Checking for post-build
Performing post-build step
Checking if email needs to be generated
Email was triggered for: Failure - Any
Sending email for trigger: Failure - Any
Sending mail from default account using System Admin e-mail address