FreeBSD-main-amd64-test - Build #25105 - Failure
Date: Mon, 15 Apr 2024 17:16:32 UTC
FreeBSD-main-amd64-test - Build #25105 (303dea74c2cb3a41fba455fce8577993e637c3da) - Failure
Build information: https://ci.FreeBSD.org/job/FreeBSD-main-amd64-test/25105/
Full change log: https://ci.FreeBSD.org/job/FreeBSD-main-amd64-test/25105/changes
Full build log: https://ci.FreeBSD.org/job/FreeBSD-main-amd64-test/25105/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)
303dea74c2cb3a41fba455fce8577993e637c3da by stevek:
iflib: Fix compiler warnings
The end of the build log:
[...truncated 4.90 MiB...]
lo0: link state changed to UP
epair0a: link state changed to DOWN
epair0b: link state changed to DOWN
passed [0.475s]
sys/net/routing/test_rtsock_multipath.py:TestRtmMultipath::test_rtm_multipath4_getroute -> epair0a: Ethernet address: 02:0b:06:79:eb:0a
epair0b: Ethernet address: 02:0b:06:79:eb: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.476s]
sys/net/routing/test_rtsock_multipath.py:TestRtmMultipath::test_rtm_multipath6[change_new_weight1] -> epair0a: Ethernet address: 02:44:7f:e0:87:0a
epair0b: Ethernet address: 02:44:7f:e0:87: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.520s]
sys/net/routing/test_rtsock_multipath.py:TestRtmMultipath::test_rtm_multipath6[change_new_weight2] -> epair0a: Ethernet address: 02:d2:54:16:5a:0a
epair0b: Ethernet address: 02:d2:54:16:5a: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.529s]
sys/net/routing/test_rtsock_multipath.py:TestRtmMultipath::test_rtm_multipath6[change_new_weight3] -> epair0a: Ethernet address: 02:7a:fd:38:3e:0a
epair0b: Ethernet address: 02:7a:fd:38:3e: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.532s]
sys/net/routing/test_rtsock_multipath.py:TestRtmMultipath::test_rtm_multipath6[change_same_weight1] -> epair0a: Ethernet address: 02:1e:9f:6a:6b:0a
epair0b: Ethernet address: 02:1e:9f:6a:6b: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.533s]
sys/net/routing/test_rtsock_multipath.py:TestRtmMultipath::test_rtm_multipath6[change_same_weight2] -> epair0a: Ethernet address: 02:59:8a:bc:aa:0a
epair0b: Ethernet address: 02:59:8a:bc:aa: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.544s]
sys/net/routing/test_rtsock_multipath.py:TestRtmMultipath::test_rtm_multipath6[correctness1] -> epair0a: Ethernet address: 02:6f:e6:f2:51:0a
epair0b: Ethernet address: 02:6f:e6:f2:51: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.556s]
sys/net/routing/test_rtsock_multipath.py:TestRtmMultipath::test_rtm_multipath6[correctness2] -> epair0a: Ethernet address: 02:c7:50:73:4f:0a
epair0b: Ethernet address: 02:c7:50:73:4f: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.560s]
sys/net/routing/test_rtsock_multipath.py:TestRtmMultipath::test_rtm_multipath6[transition_multi] -> epair0a: Ethernet address: 02:14:8f:c8:6f:0a
epair0b: Ethernet address: 02:14:8f:c8:6f: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.523s]
sys/net/routing/test_rtsock_multipath.py:TestRtmMultipath::test_rtm_multipath6[transition_single1] -> epair0a: Ethernet address: 02:2e:db:f4:68:0a
epair0b: Ethernet address: 02:2e:db:f4:68: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.542s]
sys/net/routing/test_rtsock_multipath.py:TestRtmMultipath::test_rtm_multipath6[transition_single2] -> epair0a: Ethernet address: 02:5b:51:fe:5d:0a
epair0b: Ethernet address: 02:5b:51:fe:5d: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.522s]
sys/net/routing/test_rtsock_multipath.py:TestRtmMultipath::test_rtm_multipath6[weight1] -> epair0a: Ethernet address: 02:42:57:9e:29:0a
epair0b: Ethernet address: 02:42:57:9e:29: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.528s]
sys/net/routing/test_rtsock_multipath.py:TestRtmMultipath::test_rtm_multipath6[weight2] -> epair0a: Ethernet address: 02:c7:49:19:04:0a
epair0b: Ethernet address: 02:c7:49:19:04: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.509s]
sys/net/routing/test_rtsock_multipath.py:TestRtmMultipath::test_rtm_multipath6[weight3_max0] -> epair0a: Ethernet address: 02:0e:0f:78:37:0a
epair0b: Ethernet address: 02:0e:0f:78:37: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.528s]
sys/net/routing/test_rtsock_multipath.py:TestRtmMultipath::test_rtm_multipath6[weight3_max1] -> epair0a: Ethernet address: 02:fd:d8:23:f2:0a
epair0b: Ethernet address: 02:fd:d8:23:f2: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.516s]
sys/net/routing/test_rtsock_multipath.py:TestRtmMultipath::test_rtm_multipath6_add_same_eexist -> epair0a: Ethernet address: 02:c9:0d:a4:0c:0a
epair0b: Ethernet address: 02:c9:0d:a4:0c: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.510s]
sys/net/routing/test_rtsock_multipath.py:TestRtmMultipath::test_rtm_multipath6_change_unknown_esrch -> epair0a: Ethernet address: 02:14:92:a6:89:0a
epair0b: Ethernet address: 02:14:92:a6:89: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.476s]
sys/net/routing/test_rtsock_multipath.py:TestRtmMultipath::test_rtm_multipath6_del_unknown_esrch -> epair0a: Ethernet address: 02:37:f0:ff:cd:0a
epair0b: Ethernet address: 02:37:f0:ff:cd: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.487s]
sys/net/routing/test_rtsock_multipath.py:TestRtmMultipath::test_rtm_multipath6_getroute -> epair0a: Ethernet address: 02:85:06:1f:5d:0a
epair0b: Ethernet address: 02:85:06:1f:5d: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.508s]
sys/net/routing/test_rtsock_ops:socket_rtsock_openclose -> passed [0.007s]
sys/netgraph/basic:message -> passed [0.138s]
sys/netgraph/basic:node -> passed [0.111s]
sys/netgraph/basic:queuelimit -> expected_failure: Queue full (320): 1 checks failed as expected; see output for more details [0.072s]
sys/netgraph/basic:same_name -> failed in ng_con_part2()
passed [0.009s]
sys/netgraph/basic:send_recv -> passed [0.061s]
sys/netgraph/bridge:basic -> passed [0.445s]
sys/netgraph/bridge:loop -> passed [0.118s]
sys/netgraph/bridge:many_broadcasts -> expected_failure: netgraph queue full (191): 1 checks failed as expected; see output for more details [11.807s]
sys/netgraph/bridge:many_unicasts -> panic: malloc(M_WAITOK) with sleeping prohibited
cpuid = 1
time = 1713201391
KDB: stack backtrace:
db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame 0xfffffe00a7255af0
vpanic() at vpanic+0x135/frame 0xfffffe00a7255c20
panic() at panic+0x43/frame 0xfffffe00a7255c80
malloc_dbg() at malloc_dbg+0xe2/frame 0xfffffe00a7255ca0
malloc() at malloc+0x2c/frame 0xfffffe00a7255ce0
alloc_unr_specific() at alloc_unr_specific+0x42/frame 0xfffffe00a7255d30
ng_bridge_newhook() at ng_bridge_newhook+0x118/frame 0xfffffe00a7255db0
ng_con_part2() at ng_con_part2+0x9b/frame 0xfffffe00a7255df0
ng_apply_item() at ng_apply_item+0x195/frame 0xfffffe00a7255e80
ngthread() at ngthread+0x26a/frame 0xfffffe00a7255ef0
fork_exit() at fork_exit+0x82/frame 0xfffffe00a7255f30
fork_trampoline() at fork_trampoline+0xe/frame 0xfffffe00a7255f30
--- trap 0xc, rip = 0x3713a406e2fa, rsp = 0x37139fe89658, rbp = 0x37139fe89670 ---
KDB: enter: panic
[ thread pid 79610 tid 101608 ]
Stopped at kdb_enter+0x33: movq $0,0x10524b2(%rip)
db:0:kdb.enter.panic> show pcpu
cpuid = 1
dynamic pcpu = 0xfffffe008f7d7380
curthread = 0xfffff800050bc000: pid 79610 tid 101608 critnest 1 "ng_queue0"
curpcb = 0xfffff800050bc520
fpcurthread = none
idlethread = 0xfffff800038a5000: tid 100004 "idle: cpu1"
self = 0xffffffff82411000
curpmap = 0xffffffff81b87ef0
tssp = 0xffffffff82411384
rsp0 = 0xfffffe00a7256000
kcr3 = 0x800000000237e003
ucr3 = 0xffffffffffffffff
scr3 = 0x20a9b1fcd
gs32p = 0xffffffff82411404
ldt = 0xffffffff82411444
tss = 0xffffffff82411434
curvnet = 0xfffff800030f6000
spin locks held:
db:0:kdb.enter.panic> reset
Uptime: 58m22s
+ rc=0
+ echo 'bhyve return code = 0'
bhyve return code = 0
+ sudo /usr/sbin/bhyvectl '--vm=testvm-main-amd64-25105' --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 ./run.sh
x ./disable-zfs-tests.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/jenkins5572358726090212006.sh
+ ./freebsd-ci/artifact/post-link.py
Post link: {'job_name': 'FreeBSD-main-amd64-test', 'commit': '303dea74c2cb3a41fba455fce8577993e637c3da', 'branch': 'main', 'target': 'amd64', 'target_arch': 'amd64', 'link_type': 'latest_tested'}
"Link created: main/latest_tested/amd64/amd64 -> ../../303dea74c2cb3a41fba455fce8577993e637c3da/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