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

Reply: jenkins-admin_a_FreeBSD.org: "FreeBSD-main-amd64-test - Build #22945 - Still Failing"
Go to: [ bottom of page ] [ top of archives ] [ this month ]
From: <jenkins-admin_at_FreeBSD.org>
Date: Wed, 08 Feb 2023 18:35:53 UTC
FreeBSD-main-amd64-test - Build #22944 (8b418c83d175fde3b1f65210509ddcf2ac248d9f) - Failure

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

8b418c83d175fde3b1f65210509ddcf2ac248d9f by des:
cp: Adjust the sparse file tests.



The end of the build log:

[...truncated 3.97 MB...]
epair0b: link state changed to DOWN
epair0a: link state changed to DOWN
epair1a: link state changed to DOWN
epair1b: link state changed to DOWN
epair2a: link state changed to DOWN
epair2b: link state changed to DOWN
passed  [2.349s]
sys/netpfil/common/nat:ipfw_basic  ->  epair0a: Ethernet address: 02:2e:54:1f:7e:0a
epair0b: Ethernet address: 02:2e:54:1f:7e:0b
epair0a: link state changed to UP
epair0b: link state changed to UP
epair1a: Ethernet address: 02:95:36:9e:1c:0a
epair1b: Ethernet address: 02:95:36:9e:1c:0b
epair1a: link state changed to UP
epair1b: link state changed to UP
epair2a: Ethernet address: 02:1b:58:c5:47:0a
epair2b: Ethernet address: 02:1b:58:c5:47:0b
epair2a: link state changed to UP
epair2b: link state changed to UP
epair0b: link state changed to DOWN
epair0a: link state changed to DOWN
epair1a: link state changed to DOWN
epair1b: link state changed to DOWN
epair2a: link state changed to DOWN
epair2b: link state changed to DOWN
passed  [2.340s]
sys/netpfil/common/nat:ipfw_cgn  ->  epair0a: Ethernet address: 02:7a:f0:13:9b:0a
epair0b: Ethernet address: 02:7a:f0:13:9b:0b
epair0a: link state changed to UP
epair0b: link state changed to UP
epair1a: Ethernet address: 02:50:ff:fb:7c:0a
epair1b: Ethernet address: 02:50:ff:fb:7c:0b
epair1a: link state changed to UP
epair1b: link state changed to UP
epair2a: Ethernet address: 02:ce:84:ce:34:0a
epair2b: Ethernet address: 02:ce:84:ce:34:0b
epair2a: link state changed to UP
epair2b: link state changed to UP
epair0b: link state changed to DOWN
epair0a: link state changed to DOWN
epair1a: link state changed to DOWN
epair1b: link state changed to DOWN
epair2a: link state changed to DOWN
epair2b: link state changed to DOWN
passed  [2.560s]
sys/netpfil/common/nat:ipfw_portalias  ->  epair0a: Ethernet address: 02:6a:82:ef:e7:0a
epair0b: Ethernet address: 02:6a:82:ef:e7:0b
epair0a: link state changed to UP
epair0b: link state changed to UP
epair1a: Ethernet address: 02:e2:d0:39:ce:0a
epair1b: Ethernet address: 02:e2:d0:39:ce:0b
epair1a: link state changed to UP
epair1b: link state changed to UP
epair2a: Ethernet address: 02:bc:20:3d:7b:0a
epair2b: Ethernet address: 02:bc:20:3d:7b:0b
epair2a: link state changed to UP
epair2b: link state changed to UP
epair0b: link state changed to DOWN
epair0a: link state changed to DOWN
epair1a: link state changed to DOWN
epair1b: link state changed to DOWN
epair2a: link state changed to DOWN
epair2b: link state changed to DOWN
passed  [2.356s]
sys/netpfil/common/nat:ipfw_userspace_nat  ->  epair0a: Ethernet address: 02:82:69:63:43:0a
epair0b: Ethernet address: 02:82:69:63:43:0b
epair0a: link state changed to UP
epair0b: link state changed to UP
epair1a: Ethernet address: 02:53:20:17:92:0a
epair1b: Ethernet address: 02:53:20:17:92:0b
epair1a: link state changed to UP
epair1b: link state changed to UP
epair2a: Ethernet address: 02:12:ef:f7:ad:0a
epair2b: Ethernet address: 02:12:ef:f7:ad:0b
epair2a: link state changed to UP
epair2b: link state changed to UP
2023-02-08T18:35:32.851530+00:00 - natd 19778 - - Aliasing to 198.51.100.1, mtu 1500 bytes
epair0b: link state changed to DOWN
epair0a: link state changed to DOWN
epair1a: link state changed to DOWN
epair1b: link state changed to DOWN
epair2a: link state changed to DOWN
epair2b: link state changed to DOWN
passed  [2.338s]
sys/netpfil/common/nat:pf_basic  ->  epair0a: Ethernet address: 02:bf:d9:65:39:0a
epair0b: Ethernet address: 02:bf:d9:65:39:0b
epair0a: link state changed to UP
epair0b: link state changed to UP
epair1a: Ethernet address: 02:4a:58:22:f4:0a
epair1b: Ethernet address: 02:4a:58:22:f4:0b
epair1a: link state changed to UP
epair1b: link state changed to UP
epair2a: Ethernet address: 02:63:67:17:7d:0a
epair2b: Ethernet address: 02:63:67:17:7d:0b
epair2a: link state changed to UP
epair2b: link state changed to UP
*** /usr/src/contrib/kyua/utils/process/executor.cpp:822: Invariant check failed: PID 20051 already in all_exec_handles; not properly cleaned up or reused too fast
*** Fatal signal 6 received
*** Log file is /.kyua/logs/kyua.20230208-175615.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
epair0b: link state changed to DOWN
epair0a: link state changed to DOWN
epair1a: link state changed to DOWN
epair1b: link state changed to DOWN
epair2a: link state changed to DOWN
epair2b: link state changed to DOWN
pid 781 (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 ./run-kyua.sh
a ./disable-notyet-tests.sh
a ./auto-shutdown
a ./disable-zfs-tests.sh
a ./disable-dtrace-tests.sh
a ./run.sh
+ [ -f /meta/auto-shutdown ]
+ uname -p
+ shutdown -p now
Shutdown NOW!
shutdown: [pid 20099]
+ 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-02-08T18:35:45.742185+00:00 - shutdown 20099 - - 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... 
Syncing disks, vnodes remaining... 1 0 done
All buffers synced.
lock order reversal:
 1st 0xfffff8011aa6e230 ufs (ufs, lockmgr) @ /usr/src/sys/kern/vfs_mount.c:2158
 2nd 0xfffff8011a8eacb0 tarfsz (tarfsz, lockmgr) @ /usr/src/sys/fs/tarfs/tarfs_io.c:700
lock order tarfsz -> ufs established at:
#0 0xffffffff80c5f3fd at witness_checkorder+0x32d
#1 0xffffffff80bbabdc at lockmgr_lock_flags+0x7c
#2 0xffffffff80f52b9c at ffs_lock+0x6c
#3 0xffffffff80cf9b04 at _vn_lock+0x54
#4 0xffffffff828899bd at tarfs_zread+0x1fd
#5 0xffffffff811b3e34 at VOP_READ_APV+0x34
#6 0xffffffff82889092 at tarfs_io_read+0x92
#7 0xffffffff828891d2 at tarfs_io_read_buf+0x52
#8 0xffffffff8288c6f3 at tarfs_alloc_mount+0x2d3
#9 0xffffffff8288bf71 at tarfs_mount+0x3b1
#10 0xffffffff80cd9df0 at vfs_domount_first+0x250
#11 0xffffffff80cd6351 at vfs_domount+0x2f1
#12 0xffffffff80cd4ce5 at vfs_donmount+0x895
#13 0xffffffff80cd4419 at sys_nmount+0x69
#14 0xffffffff810e3bc4 at amd64_syscall+0x6b4
#15 0xffffffff810b615b at fast_syscall_common+0xf8
lock order ufs -> tarfsz attempted at:
#0 0xffffffff80c5fccd at witness_checkorder+0xbfd
#1 0xffffffff80bbace2 at lockmgr_lock_flags+0x182
#2 0xffffffff80cf9b04 at _vn_lock+0x54
#3 0xffffffff828894cb at tarfs_io_fini+0x3b
#4 0xffffffff8288d457 at tarfs_free_mount+0x87
#5 0xffffffff8288c055 at tarfs_unmount+0x65
#6 0xffffffff80cd7333 at dounmount+0x7c3
#7 0xffffffff80ce3cda at vfs_unmountall+0x6a
#8 0xffffffff80cb486e at bufshutdown+0x34e
#9 0xffffffff80bed544 at kern_reboot+0x764
#10 0xffffffff80becd88 at sys_reboot+0x3a8
#11 0xffffffff810e3bc4 at amd64_syscall+0x6b4
#12 0xffffffff810b615b at fast_syscall_common+0xf8
lock order reversal:
 1st 0xfffff80003b4b070 devfs (devfs, lockmgr) @ /usr/src/sys/kern/vfs_mount.c:2158
 2nd 0xfffff80006b1be70 fdescfs (fdescfs, lockmgr) @ /usr/src/sys/kern/vfs_subr.c:3043
lock order devfs -> fdescfs attempted at:
#0 0xffffffff80c5fccd at witness_checkorder+0xbfd
#1 0xffffffff80bbace2 at lockmgr_lock_flags+0x182
#2 0xffffffff80cf9b04 at _vn_lock+0x54
#3 0xffffffff80ce148f at vget_finish+0x4f
#4 0xffffffff82710242 at fdesc_root+0x22
#5 0xffffffff80ce24ec at vflush+0x4c
#6 0xffffffff827101f2 at fdesc_unmount+0x72
#7 0xffffffff80cd7333 at dounmount+0x7c3
#8 0xffffffff80ce3cda at vfs_unmountall+0x6a
#9 0xffffffff80cb486e at bufshutdown+0x34e
#10 0xffffffff80bed544 at kern_reboot+0x764
#11 0xffffffff80becd88 at sys_reboot+0x3a8
#12 0xffffffff810e3bc4 at amd64_syscall+0x6b4
#13 0xffffffff810b615b at fast_syscall_common+0xf8
pid 495 (devd), jid 0, uid 0: exited on signal 11
Uptime: 39m37s
Khelp module "ertt" can't unload until its refcount drops from 4 to 0.
acpi0: Powering system off
+ rc=0
+ echo 'bhyve return code = 0'
bhyve return code = 0
+ sudo /usr/sbin/bhyvectl '--vm=testvm-main-amd64-22944' --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 ./run-kyua.sh
x ./disable-notyet-tests.sh
x ./auto-shutdown
x ./disable-zfs-tests.sh
x ./disable-dtrace-tests.sh
x ./run.sh
+ 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/jenkins4837211814396466034.sh
+ ./freebsd-ci/artifact/post-link.py
Post link: {'job_name': 'FreeBSD-main-amd64-test', 'commit': '8b418c83d175fde3b1f65210509ddcf2ac248d9f', 'branch': 'main', 'target': 'amd64', 'target_arch': 'amd64', 'link_type': 'latest_tested'}
"Link created: main/latest_tested/amd64/amd64 -> ../../8b418c83d175fde3b1f65210509ddcf2ac248d9f/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