bots libvirt: segfault when attach-disk source is a directory

libvirt: segfault when attach-disk source is a directory

Open tomasmatus opened this issue 7 months ago • 1 comments

upstream: https://gitlab.com/libvirt/libvirt/-/issues/765

Apr 11 '25 10:04 tomasmatus

arch Ooops, it happened again

#2  0x00007228ddde4599 n/a (libvirt_driver_qemu.so + 0x10b599)
#3  0x00007228e72c3e94 n/a (libgio-2.0.so.0 + 0x93e94)
#4  0x00007228e796c1e4 n/a (libglib-2.0.so.0 + 0x5e1e4)
#5  0x00007228e79cfe97 n/a (libglib-2.0.so.0 + 0xc1e97)
#6  0x00007228e796cee7 g_main_loop_run (libglib-2.0.so.0 + 0x5eee7)
#7  0x00007228e74cac23 n/a (libvirt.so.0 + 0xcac23)
#8  0x00007228e79a3b3e n/a (libglib-2.0.so.0 + 0x95b3e)
#9  0x00007228e707770a n/a (libc.so.6 + 0x9570a)
#10 0x00007228e70fbaac n/a (libc.so.6 + 0x119aac)
ELF object binary architecture: AMD x86-64
Wrote JS log to TestMachinesDisks-testAddDiskCustomPath-arch-127.0.0.2-2201-FAIL.js.log
Journal extracted to TestMachinesDisks-testAddDiskCustomPath-arch-127.0.0.2-2201-FAIL.log.gz
Core dumps downloaded to /work/make-checkout-workdir/TestMachinesDisks-testAddDiskCustomPath-arch-127.0.0.2-2201-FAIL.core
Stopping 'libvirtd.service', but its triggering units are still active:
libvirtd.socket, libvirtd-ro.socket, libvirtd-admin.socket
Traceback (most recent call last):
  File "/work/make-checkout-workdir/test/machineslib.py", line 573, in tearDown
    super().tearDown()
    ~~~~~~~~~~~~~~~~^^
  File "/work/make-checkout-workdir/test/common/testlib.py", line 1990, in tearDown
    self.check_journal_messages()
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~^^
  File "/work/make-checkout-workdir/test/common/testlib.py", line 2253, in check_journal_messages
    raise Error(UNEXPECTED_MESSAGE + "journal messages:\n" + first)
testlib.Error: FAIL: Test completed, but found unexpected journal messages:
Process 4585 (libvirtd) of user 0 terminated abnormally with signal 11/SEGV, processing...

# Result testAddDiskCustomPath (__main__.TestMachinesDisks.testAddDiskCustomPath) failed
# 1 TEST FAILED [80s on 0798335aa802]
not ok 25 /work/make-checkout-workdir/test/check-machines-disks TestMachinesDisks.testAddDiskCustomPath [ND@0]

First occurrence: 2025-04-11T11:29:26.369545+00:00 | revision 51efdbfd211c6463331d0bd6cd83c2444c75f7b5 Times recorded: 1 Latest occurrences:

2025-04-11T11:29:26.369545+00:00 | revision 51efdbfd211c6463331d0bd6cd83c2444c75f7b5

#3  0x00007e014b3c4a06 ppoll (libc.so.6 + 0x10ca06)
#4  0x00007e014b769f67 n/a (libglib-2.0.so.0 + 0xc1f67)
#5  0x00007e014b705615 g_main_context_iteration (libglib-2.0.so.0 + 0x5d615)
#6  0x00007e014b8caf85 virEventGLibRunOnce (libvirt.so.0 + 0xcaf85)
#7  0x00007e014b9fc079 virNetDaemonRun (libvirt.so.0 + 0x1fc079)
#8  0x00005abf042b4ad6 main (/usr/bin/libvirtd + 0x2ead6)
#9  0x00007e014b2df488 n/a (libc.so.6 + 0x27488)
#10 0x00007e014b2df54c __libc_start_main (libc.so.6 + 0x2754c)
#11 0x00005abf042b53e5 _start (/usr/bin/libvirtd + 0x2f3e5)
ELF object binary architecture: AMD x86-64
Wrote JS log to TestMachinesDisks-testAddDiskCustomPath-arch-127.0.0.2-2201-FAIL-1.js.log
Journal extracted to TestMachinesDisks-testAddDiskCustomPath-arch-127.0.0.2-2201-FAIL-1.log.gz
Core dumps downloaded to /work/make-checkout-workdir/TestMachinesDisks-testAddDiskCustomPath-arch-127.0.0.2-2201-FAIL.core
Stopping 'libvirtd.service', but its triggering units are still active:
libvirtd-admin.socket, libvirtd.socket, libvirtd-ro.socket
Traceback (most recent call last):
  File "/work/make-checkout-workdir/test/machineslib.py", line 573, in tearDown
    super().tearDown()
    ~~~~~~~~~~~~~~~~^^
  File "/work/make-checkout-workdir/test/common/testlib.py", line 1990, in tearDown
    self.check_journal_messages()
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~^^
  File "/work/make-checkout-workdir/test/common/testlib.py", line 2253, in check_journal_messages
    raise Error(UNEXPECTED_MESSAGE + "journal messages:\n" + first)
testlib.Error: FAIL: Test completed, but found unexpected journal messages:
Process 6622 (libvirtd) of user 0 terminated abnormally with signal 11/SEGV, processing...

# Result testAddDiskCustomPath (__main__.TestMachinesDisks.testAddDiskCustomPath) failed
# 1 TEST FAILED [56s on 6a5393ca7900]
not ok 25 /work/make-checkout-workdir/test/check-machines-disks TestMachinesDisks.testAddDiskCustomPath [ND@0]

First occurrence: 2025-04-13T08:00:17.685880+00:00 | revision e68be9ed939537c9752c304046b2690534cc77aa Times recorded: 1 Latest occurrences:

2025-04-13T08:00:17.685880+00:00 | revision e68be9ed939537c9752c304046b2690534cc77aa

#2  0x000078c3b81eb599 n/a (libvirt_driver_qemu.so + 0x10b599)
#3  0x000078c3bde64e94 n/a (libgio-2.0.so.0 + 0x93e94)
#4  0x000078c3be5351e4 n/a (libglib-2.0.so.0 + 0x5e1e4)
#5  0x000078c3be598e97 n/a (libglib-2.0.so.0 + 0xc1e97)
#6  0x000078c3be535ee7 g_main_loop_run (libglib-2.0.so.0 + 0x5eee7)
#7  0x000078c3be0cac23 n/a (libvirt.so.0 + 0xcac23)
#8  0x000078c3be56cb3e n/a (libglib-2.0.so.0 + 0x95b3e)
#9  0x000078c3bdc4670a n/a (libc.so.6 + 0x9570a)
#10 0x000078c3bdccaaac n/a (libc.so.6 + 0x119aac)
ELF object binary architecture: AMD x86-64
Wrote JS log to TestMachinesDisks-testAddDiskCustomPath-arch-127.0.0.2-2201-FAIL.js.log
Journal extracted to TestMachinesDisks-testAddDiskCustomPath-arch-127.0.0.2-2201-FAIL.log.gz
Core dumps downloaded to /work/make-checkout-workdir/TestMachinesDisks-testAddDiskCustomPath-arch-127.0.0.2-2201-FAIL.core
Stopping 'libvirtd.service', but its triggering units are still active:
libvirtd.socket, libvirtd-admin.socket, libvirtd-ro.socket
Traceback (most recent call last):
  File "/work/make-checkout-workdir/test/machineslib.py", line 573, in tearDown
    super().tearDown()
    ~~~~~~~~~~~~~~~~^^
  File "/work/make-checkout-workdir/test/common/testlib.py", line 1990, in tearDown
    self.check_journal_messages()
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~^^
  File "/work/make-checkout-workdir/test/common/testlib.py", line 2253, in check_journal_messages
    raise Error(UNEXPECTED_MESSAGE + "journal messages:\n" + first)
testlib.Error: FAIL: Test completed, but found unexpected journal messages:
Process 4542 (libvirtd) of user 0 terminated abnormally with signal 11/SEGV, processing...

# Result testAddDiskCustomPath (__main__.TestMachinesDisks.testAddDiskCustomPath) failed
# 1 TEST FAILED [46s on a09939c80bce]
not ok 25 /work/make-checkout-workdir/test/check-machines-disks TestMachinesDisks.testAddDiskCustomPath [ND@0]

First occurrence: 2025-04-14T05:23:11.043492+00:00 | revision 56b863270f1c838ddc8cec59803b5ea57d66121b Times recorded: 1 Latest occurrences:

2025-04-14T05:23:11.043492+00:00 | revision 56b863270f1c838ddc8cec59803b5ea57d66121b

#2  0x00007bfeb01e7599 n/a (libvirt_driver_qemu.so + 0x10b599)
#3  0x00007bfeb7f0ce94 n/a (libgio-2.0.so.0 + 0x93e94)
#4  0x00007bfeb81061e4 n/a (libglib-2.0.so.0 + 0x5e1e4)
#5  0x00007bfeb8169e97 n/a (libglib-2.0.so.0 + 0xc1e97)
#6  0x00007bfeb8106ee7 g_main_loop_run (libglib-2.0.so.0 + 0x5eee7)
#7  0x00007bfeb82cac23 n/a (libvirt.so.0 + 0xcac23)
#8  0x00007bfeb813db3e n/a (libglib-2.0.so.0 + 0x95b3e)
#9  0x00007bfeb7cee70a n/a (libc.so.6 + 0x9570a)
#10 0x00007bfeb7d72aac n/a (libc.so.6 + 0x119aac)
ELF object binary architecture: AMD x86-64
Wrote JS log to TestMachinesDisks-testAddDiskCustomPath-arch-127.0.0.2-2301-FAIL.js.log
Journal extracted to TestMachinesDisks-testAddDiskCustomPath-arch-127.0.0.2-2301-FAIL.log.gz
Core dumps downloaded to /work/make-checkout-workdir/TestMachinesDisks-testAddDiskCustomPath-arch-127.0.0.2-2301-FAIL.core
Stopping 'libvirtd.service', but its triggering units are still active:
libvirtd-admin.socket, libvirtd.socket, libvirtd-ro.socket
Traceback (most recent call last):
  File "/work/make-checkout-workdir/test/machineslib.py", line 573, in tearDown
    super().tearDown()
    ~~~~~~~~~~~~~~~~^^
  File "/work/make-checkout-workdir/test/common/testlib.py", line 1990, in tearDown
    self.check_journal_messages()
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~^^
  File "/work/make-checkout-workdir/test/common/testlib.py", line 2253, in check_journal_messages
    raise Error(UNEXPECTED_MESSAGE + "journal messages:\n" + first)
testlib.Error: FAIL: Test completed, but found unexpected journal messages:
Process 4570 (libvirtd) of user 0 terminated abnormally with signal 11/SEGV, processing...

# Result testAddDiskCustomPath (__main__.TestMachinesDisks.testAddDiskCustomPath) failed
# 1 TEST FAILED [73s on 24bfe9e1c08c]
not ok 25 /work/make-checkout-workdir/test/check-machines-disks TestMachinesDisks.testAddDiskCustomPath [ND@1]

First occurrence: 2025-04-14T05:26:03.826505+00:00 | revision a71a2681a8e54176ad046a06c61d33d3e4561e9f Times recorded: 1 Latest occurrences:

2025-04-14T05:26:03.826505+00:00 | revision a71a2681a8e54176ad046a06c61d33d3e4561e9f

#0  0x00007849f0355be2 n/a (libc.so.6 + 0x9dbe2)
#1  0x00007849f0349e33 n/a (libc.so.6 + 0x91e33)
#2  0x00007849f034a4bc n/a (libc.so.6 + 0x924bc)
#3  0x00007849f034cc0e pthread_cond_wait (libc.so.6 + 0x94c0e)
#4  0x00007849f091d3c3 virCondWait (libvirt.so.0 + 0x11d3c3)
#5  0x00007849f09269c4 n/a (libvirt.so.0 + 0x1269c4)
#6  0x00007849f0925ec3 n/a (libvirt.so.0 + 0x125ec3)
#7  0x00007849f034d70a n/a (libc.so.6 + 0x9570a)
#8  0x00007849f03d1aac n/a (libc.so.6 + 0x119aac)
ELF object binary architecture: AMD x86-64
Wrote JS log to TestMachinesDisks-testAddDiskCustomPath-arch-127.0.0.2-2301-FAIL.js.log
Journal extracted to TestMachinesDisks-testAddDiskCustomPath-arch-127.0.0.2-2301-FAIL.log.gz
Core dumps downloaded to /work/make-checkout-workdir/TestMachinesDisks-testAddDiskCustomPath-arch-127.0.0.2-2301-FAIL.core
Stopping 'libvirtd.service', but its triggering units are still active:
libvirtd.socket, libvirtd-ro.socket, libvirtd-admin.socket
Traceback (most recent call last):
  File "/work/make-checkout-workdir/test/machineslib.py", line 573, in tearDown
    super().tearDown()
    ~~~~~~~~~~~~~~~~^^
  File "/work/make-checkout-workdir/test/common/testlib.py", line 1990, in tearDown
    self.check_journal_messages()
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~^^
  File "/work/make-checkout-workdir/test/common/testlib.py", line 2253, in check_journal_messages
    raise Error(UNEXPECTED_MESSAGE + "journal messages:\n" + first)
testlib.Error: FAIL: Test completed, but found unexpected journal messages:
Process 3475 (libvirtd) of user 0 terminated abnormally with signal 11/SEGV, processing...

# Result testAddDiskCustomPath (__main__.TestMachinesDisks.testAddDiskCustomPath) failed
# 1 TEST FAILED [106s on 8f9dd60ae344]
not ok 25 /work/make-checkout-workdir/test/check-machines-disks TestMachinesDisks.testAddDiskCustomPath [ND@1]

First occurrence: 2025-04-14T13:06:10.802101+00:00 | revision 4957ae6e3b265ae9b39bf47bb70ad134f1a6c220 Times recorded: 1 Latest occurrences:

2025-04-14T13:06:10.802101+00:00 | revision 4957ae6e3b265ae9b39bf47bb70ad134f1a6c220

#0  0x00007d18b4583be2 n/a (libc.so.6 + 0x9dbe2)
#1  0x00007d18b4577e33 n/a (libc.so.6 + 0x91e33)
#2  0x00007d18b45784bc n/a (libc.so.6 + 0x924bc)
#3  0x00007d18b457ac0e pthread_cond_wait (libc.so.6 + 0x94c0e)
#4  0x00007d18b4b1d3c3 virCondWait (libvirt.so.0 + 0x11d3c3)
#5  0x00007d18b4b269c4 n/a (libvirt.so.0 + 0x1269c4)
#6  0x00007d18b4b25ec3 n/a (libvirt.so.0 + 0x125ec3)
#7  0x00007d18b457b70a n/a (libc.so.6 + 0x9570a)
#8  0x00007d18b45ffaac n/a (libc.so.6 + 0x119aac)
ELF object binary architecture: AMD x86-64
Wrote JS log to TestMachinesDisks-testAddDiskCustomPath-arch-127.0.0.2-2301-FAIL.js.log
Journal extracted to TestMachinesDisks-testAddDiskCustomPath-arch-127.0.0.2-2301-FAIL.log.gz
Core dumps downloaded to /work/make-checkout-workdir/TestMachinesDisks-testAddDiskCustomPath-arch-127.0.0.2-2301-FAIL.core
Stopping 'libvirtd.service', but its triggering units are still active:
libvirtd.socket, libvirtd-admin.socket, libvirtd-ro.socket
Traceback (most recent call last):
  File "/work/make-checkout-workdir/test/machineslib.py", line 573, in tearDown
    super().tearDown()
    ~~~~~~~~~~~~~~~~^^
  File "/work/make-checkout-workdir/test/common/testlib.py", line 1990, in tearDown
    self.check_journal_messages()
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~^^
  File "/work/make-checkout-workdir/test/common/testlib.py", line 2253, in check_journal_messages
    raise Error(UNEXPECTED_MESSAGE + "journal messages:\n" + first)
testlib.Error: FAIL: Test completed, but found unexpected journal messages:
Process 4575 (libvirtd) of user 0 terminated abnormally with signal 11/SEGV, processing...

# Result testAddDiskCustomPath (__main__.TestMachinesDisks.testAddDiskCustomPath) failed
# 1 TEST FAILED [53s on 69bef94b41dc]
not ok 25 /work/make-checkout-workdir/test/check-machines-disks TestMachinesDisks.testAddDiskCustomPath [ND@1]

First occurrence: 2025-04-15T18:30:33.835113+00:00 | revision b565f9364d3d17a3aab0110398e8feca9d98feef Times recorded: 1 Latest occurrences:

2025-04-15T18:30:33.835113+00:00 | revision b565f9364d3d17a3aab0110398e8feca9d98feef

#0  0x000070106f0adbe2 n/a (libc.so.6 + 0x9dbe2)
#1  0x000070106f0a1e33 n/a (libc.so.6 + 0x91e33)
#2  0x000070106f0a24bc n/a (libc.so.6 + 0x924bc)
#3  0x000070106f0a4c0e pthread_cond_wait (libc.so.6 + 0x94c0e)
#4  0x000070106f51d3c3 virCondWait (libvirt.so.0 + 0x11d3c3)
#5  0x000070106f5269c4 n/a (libvirt.so.0 + 0x1269c4)
#6  0x000070106f525ec3 n/a (libvirt.so.0 + 0x125ec3)
#7  0x000070106f0a570a n/a (libc.so.6 + 0x9570a)
#8  0x000070106f129aac n/a (libc.so.6 + 0x119aac)
ELF object binary architecture: AMD x86-64
Wrote JS log to TestMachinesDisks-testAddDiskCustomPath-arch-127.0.0.2-2401-FAIL.js.log
Journal extracted to TestMachinesDisks-testAddDiskCustomPath-arch-127.0.0.2-2401-FAIL.log.gz
Core dumps downloaded to /work/make-checkout-workdir/TestMachinesDisks-testAddDiskCustomPath-arch-127.0.0.2-2401-FAIL.core
Stopping 'libvirtd.service', but its triggering units are still active:
libvirtd-ro.socket, libvirtd-admin.socket, libvirtd.socket
Traceback (most recent call last):
  File "/work/make-checkout-workdir/test/machineslib.py", line 573, in tearDown
    super().tearDown()
    ~~~~~~~~~~~~~~~~^^
  File "/work/make-checkout-workdir/test/common/testlib.py", line 1990, in tearDown
    self.check_journal_messages()
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~^^
  File "/work/make-checkout-workdir/test/common/testlib.py", line 2253, in check_journal_messages
    raise Error(UNEXPECTED_MESSAGE + "journal messages:\n" + first)
testlib.Error: FAIL: Test completed, but found unexpected journal messages:
Process 4496 (libvirtd) of user 0 terminated abnormally with signal 11/SEGV, processing...

# Result testAddDiskCustomPath (__main__.TestMachinesDisks.testAddDiskCustomPath) failed
# 1 TEST FAILED [144s on 1f344ff758af]
not ok 25 /work/make-checkout-workdir/test/check-machines-disks TestMachinesDisks.testAddDiskCustomPath [ND@2]

First occurrence: 2025-04-17T03:05:25.745562+00:00 | revision 06abe7e58f6786e7f0729d2e05d379328369e302 Times recorded: 1 Latest occurrences:

2025-04-17T03:05:25.745562+00:00 | revision 06abe7e58f6786e7f0729d2e05d379328369e302

#2  0x00007aa4e99e4599 n/a (libvirt_driver_qemu.so + 0x10b599)
#3  0x00007aa4f2ec3e94 n/a (libgio-2.0.so.0 + 0x93e94)
#4  0x00007aa4f35791e4 n/a (libglib-2.0.so.0 + 0x5e1e4)
#5  0x00007aa4f35dce97 n/a (libglib-2.0.so.0 + 0xc1e97)
#6  0x00007aa4f3579ee7 g_main_loop_run (libglib-2.0.so.0 + 0x5eee7)
#7  0x00007aa4f30cac23 n/a (libvirt.so.0 + 0xcac23)
#8  0x00007aa4f35b0b3e n/a (libglib-2.0.so.0 + 0x95b3e)
#9  0x00007aa4f2c7770a n/a (libc.so.6 + 0x9570a)
#10 0x00007aa4f2cfbaac n/a (libc.so.6 + 0x119aac)
ELF object binary architecture: AMD x86-64
Wrote JS log to TestMachinesDisks-testAddDiskCustomPath-arch-127.0.0.2-2301-FAIL.js.log
Journal extracted to TestMachinesDisks-testAddDiskCustomPath-arch-127.0.0.2-2301-FAIL.log.gz
Core dumps downloaded to /work/make-checkout-workdir/TestMachinesDisks-testAddDiskCustomPath-arch-127.0.0.2-2301-FAIL.core
Stopping 'libvirtd.service', but its triggering units are still active:
libvirtd-admin.socket, libvirtd-ro.socket, libvirtd.socket
Traceback (most recent call last):
  File "/work/make-checkout-workdir/test/machineslib.py", line 573, in tearDown
    super().tearDown()
    ~~~~~~~~~~~~~~~~^^
  File "/work/make-checkout-workdir/test/common/testlib.py", line 1990, in tearDown
    self.check_journal_messages()
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~^^
  File "/work/make-checkout-workdir/test/common/testlib.py", line 2253, in check_journal_messages
    raise Error(UNEXPECTED_MESSAGE + "journal messages:\n" + first)
testlib.Error: FAIL: Test completed, but found unexpected journal messages:
Process 4562 (libvirtd) of user 0 terminated abnormally with signal 11/SEGV, processing...

# Result testAddDiskCustomPath (__main__.TestMachinesDisks.testAddDiskCustomPath) failed
# 1 TEST FAILED [44s on 3a46b788c892]
not ok 25 /work/make-checkout-workdir/test/check-machines-disks TestMachinesDisks.testAddDiskCustomPath [ND@1]

First occurrence: 2025-04-18T23:00:13.491382+00:00 | revision 55be199f45016bcdbb98e335263df6cc50649ddc Times recorded: 1 Latest occurrences:

2025-04-18T23:00:13.491382+00:00 | revision 55be199f45016bcdbb98e335263df6cc50649ddc

#2  0x00007f6f5870a599 n/a (libvirt_driver_qemu.so + 0x10b599)
#3  0x00007f6f65d6be94 n/a (libgio-2.0.so.0 + 0x93e94)
#4  0x00007f6f65f061e4 n/a (libglib-2.0.so.0 + 0x5e1e4)
#5  0x00007f6f65f69e97 n/a (libglib-2.0.so.0 + 0xc1e97)
#6  0x00007f6f65f06ee7 g_main_loop_run (libglib-2.0.so.0 + 0x5eee7)
#7  0x00007f6f660cac23 n/a (libvirt.so.0 + 0xcac23)
#8  0x00007f6f65f3db3e n/a (libglib-2.0.so.0 + 0x95b3e)
#9  0x00007f6f65b1f70a n/a (libc.so.6 + 0x9570a)
#10 0x00007f6f65ba3aac n/a (libc.so.6 + 0x119aac)
ELF object binary architecture: AMD x86-64
Wrote JS log to TestMachinesDisks-testAddDiskCustomPath-arch-127.0.0.2-2201-FAIL.js.log
Journal extracted to TestMachinesDisks-testAddDiskCustomPath-arch-127.0.0.2-2201-FAIL.log.gz
Core dumps downloaded to /work/make-checkout-workdir/TestMachinesDisks-testAddDiskCustomPath-arch-127.0.0.2-2201-FAIL.core
Stopping 'libvirtd.service', but its triggering units are still active:
libvirtd.socket, libvirtd-ro.socket, libvirtd-admin.socket
Traceback (most recent call last):
  File "/work/make-checkout-workdir/test/machineslib.py", line 573, in tearDown
    super().tearDown()
    ~~~~~~~~~~~~~~~~^^
  File "/work/make-checkout-workdir/test/common/testlib.py", line 1990, in tearDown
    self.check_journal_messages()
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~^^
  File "/work/make-checkout-workdir/test/common/testlib.py", line 2253, in check_journal_messages
    raise Error(UNEXPECTED_MESSAGE + "journal messages:\n" + first)
testlib.Error: FAIL: Test completed, but found unexpected journal messages:
Process 4555 (libvirtd) of user 0 terminated abnormally with signal 11/SEGV, processing...

# Result testAddDiskCustomPath (__main__.TestMachinesDisks.testAddDiskCustomPath) failed
# 1 TEST FAILED [50s on 8c802538392e]
not ok 25 /work/make-checkout-workdir/test/check-machines-disks TestMachinesDisks.testAddDiskCustomPath [ND@0]

First occurrence: 2025-04-21T04:07:42.606952+00:00 | revision 9488a4ae32e589056ad186969056f2e206e97040 Times recorded: 1 Latest occurrences:

2025-04-21T04:07:42.606952+00:00 | revision 9488a4ae32e589056ad186969056f2e206e97040

#2  0x00007eeca5f0d599 n/a (libvirt_driver_qemu.so + 0x10b599)
#3  0x00007eecb3664e94 n/a (libgio-2.0.so.0 + 0x93e94)
#4  0x00007eecb3cfb1e4 n/a (libglib-2.0.so.0 + 0x5e1e4)
#5  0x00007eecb3d5ee97 n/a (libglib-2.0.so.0 + 0xc1e97)
#6  0x00007eecb3cfbee7 g_main_loop_run (libglib-2.0.so.0 + 0x5eee7)
#7  0x00007eecb38cac23 n/a (libvirt.so.0 + 0xcac23)
#8  0x00007eecb3d32b3e n/a (libglib-2.0.so.0 + 0x95b3e)
#9  0x00007eecb34197eb n/a (libc.so.6 + 0x957eb)
#10 0x00007eecb349d18c n/a (libc.so.6 + 0x11918c)
ELF object binary architecture: AMD x86-64
Wrote JS log to TestMachinesDisks-testAddDiskCustomPath-arch-127.0.0.2-2401-FAIL.js.log
Journal extracted to TestMachinesDisks-testAddDiskCustomPath-arch-127.0.0.2-2401-FAIL.log.gz
Core dumps downloaded to /work/make-checkout-workdir/TestMachinesDisks-testAddDiskCustomPath-arch-127.0.0.2-2401-FAIL.core
Stopping 'libvirtd.service', but its triggering units are still active:
libvirtd-admin.socket, libvirtd-ro.socket, libvirtd.socket
Traceback (most recent call last):
  File "/work/make-checkout-workdir/test/machineslib.py", line 573, in tearDown
    super().tearDown()
    ~~~~~~~~~~~~~~~~^^
  File "/work/make-checkout-workdir/test/common/testlib.py", line 1990, in tearDown
    self.check_journal_messages()
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~^^
  File "/work/make-checkout-workdir/test/common/testlib.py", line 2253, in check_journal_messages
    raise Error(UNEXPECTED_MESSAGE + "journal messages:\n" + first)
testlib.Error: FAIL: Test completed, but found unexpected journal messages:
Process 4453 (libvirtd) of user 0 terminated abnormally with signal 11/SEGV, processing...

# Result testAddDiskCustomPath (__main__.TestMachinesDisks.testAddDiskCustomPath) failed
# 1 TEST FAILED [51s on 4677ed3664a1]
not ok 25 /work/make-checkout-workdir/test/check-machines-disks TestMachinesDisks.testAddDiskCustomPath [ND@2]

First occurrence: 2025-05-12T03:15:24.828971+00:00 | revision 9b855b8a590c6f65229bfe949caec2d073839831 Times recorded: 1 Latest occurrences:

2025-05-12T03:15:24.828971+00:00 | revision 9b855b8a590c6f65229bfe949caec2d073839831

Apr 11 '25 11:04 cockpituous

debian-testing Ooops, it happened again

Please see https://chromedriver.chromium.org/security-considerations for suggestions on keeping ChromeDriver safe.
ChromeDriver was started successfully on port 34433.
Failed to try-restart sssd.service: Unit sssd.service not found.
bash: line 1: rpmquery: command not found
> error: Scrollbar test exception: TypeError: Cannot read properties of null (reading 'appendChild')
> warn: Failed to get current crypto policy: not-found ; falling back to /etc/crypto-policies/config
> warn: cockpit.format_{bytes,bits}[_per_sec](..., MiB, [object Object]) is deprecated.
> warn: could not execute head --bytes=16 head: error reading '/tmp/': Is a directory
Process 7107 (libvirtd) of user 0 terminated abnormally with signal 11/SEGV, processing...
Process 7107 (libvirtd) of user 0 dumped core.
Wrote JS log to TestMachinesDisks-testAddDiskCustomPath-debian-testing-127.0.0.2-3001-FAIL.js.log
Journal extracted to TestMachinesDisks-testAddDiskCustomPath-debian-testing-127.0.0.2-3001-FAIL.log.gz
Core dumps downloaded to /work/make-checkout-workdir/TestMachinesDisks-testAddDiskCustomPath-debian-testing-127.0.0.2-3001-FAIL.core
Stopping 'libvirtd.service', but its triggering units are still active:
libvirtd.socket, libvirtd-ro.socket, libvirtd-admin.socket
Traceback (most recent call last):
  File "/work/make-checkout-workdir/test/machineslib.py", line 573, in tearDown
    super().tearDown()
    ~~~~~~~~~~~~~~~~^^
  File "/work/make-checkout-workdir/test/common/testlib.py", line 1990, in tearDown
    self.check_journal_messages()
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~^^
  File "/work/make-checkout-workdir/test/common/testlib.py", line 2253, in check_journal_messages
    raise Error(UNEXPECTED_MESSAGE + "journal messages:\n" + first)
testlib.Error: FAIL: Test completed, but found unexpected journal messages:
Process 7107 (libvirtd) of user 0 terminated abnormally with signal 11/SEGV, processing...

# Result testAddDiskCustomPath (__main__.TestMachinesDisks.testAddDiskCustomPath) failed
# 1 TEST FAILED [46s on 810791bc2af4]
not ok 25 /work/make-checkout-workdir/test/check-machines-disks TestMachinesDisks.testAddDiskCustomPath [ND@7]

First occurrence: 2025-04-16T07:40:26.785770+00:00 | revision 19bb74962884f0abe8e787501296848853a7aa59 Times recorded: 1 Latest occurrences:

2025-04-16T07:40:26.785770+00:00 | revision 19bb74962884f0abe8e787501296848853a7aa59

Please see https://chromedriver.chromium.org/security-considerations for suggestions on keeping ChromeDriver safe.
ChromeDriver was started successfully on port 32853.
Failed to try-restart sssd.service: Unit sssd.service not found.
bash: line 1: rpmquery: command not found
> error: Scrollbar test exception: TypeError: Cannot read properties of null (reading 'appendChild')
> warn: Failed to get current crypto policy: not-found ; falling back to /etc/crypto-policies/config
> warn: cockpit.format_{bytes,bits}[_per_sec](..., MiB, [object Object]) is deprecated.
> warn: could not execute head --bytes=16 head: error reading '/tmp/': Is a directory
Process 8757 (libvirtd) of user 0 terminated abnormally with signal 11/SEGV, processing...
Process 8757 (libvirtd) of user 0 dumped core.
Wrote JS log to TestMachinesDisks-testAddDiskCustomPath-debian-testing-127.0.0.2-2301-FAIL.js.log
Journal extracted to TestMachinesDisks-testAddDiskCustomPath-debian-testing-127.0.0.2-2301-FAIL.log.gz
Core dumps downloaded to /work/make-checkout-workdir/TestMachinesDisks-testAddDiskCustomPath-debian-testing-127.0.0.2-2301-FAIL.core
Stopping 'libvirtd.service', but its triggering units are still active:
libvirtd-admin.socket, libvirtd.socket, libvirtd-ro.socket
Traceback (most recent call last):
  File "/work/make-checkout-workdir/test/machineslib.py", line 573, in tearDown
    super().tearDown()
    ~~~~~~~~~~~~~~~~^^
  File "/work/make-checkout-workdir/test/common/testlib.py", line 1990, in tearDown
    self.check_journal_messages()
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~^^
  File "/work/make-checkout-workdir/test/common/testlib.py", line 2253, in check_journal_messages
    raise Error(UNEXPECTED_MESSAGE + "journal messages:\n" + first)
testlib.Error: FAIL: Test completed, but found unexpected journal messages:
Process 8757 (libvirtd) of user 0 terminated abnormally with signal 11/SEGV, processing...

# Result testAddDiskCustomPath (__main__.TestMachinesDisks.testAddDiskCustomPath) failed
# 1 TEST FAILED [81s on 0cba19de84e5]
not ok 25 /work/make-checkout-workdir/test/check-machines-disks TestMachinesDisks.testAddDiskCustomPath [ND@1]

First occurrence: 2025-04-16T07:43:16.609600+00:00 | revision 19bb74962884f0abe8e787501296848853a7aa59 Times recorded: 1 Latest occurrences:

2025-04-16T07:43:16.609600+00:00 | revision 19bb74962884f0abe8e787501296848853a7aa59

Please see https://chromedriver.chromium.org/security-considerations for suggestions on keeping ChromeDriver safe.
ChromeDriver was started successfully on port 34963.
Failed to try-restart sssd.service: Unit sssd.service not found.
bash: line 1: rpmquery: command not found
> error: Scrollbar test exception: TypeError: Cannot read properties of null (reading 'appendChild')
> warn: Failed to get current crypto policy: not-found ; falling back to /etc/crypto-policies/config
> warn: cockpit.format_{bytes,bits}[_per_sec](..., MiB, [object Object]) is deprecated.
> warn: could not execute head --bytes=16 head: error reading '/tmp/': Is a directory
Process 6407 (libvirtd) of user 0 terminated abnormally with signal 11/SEGV, processing...
Process 6407 (libvirtd) of user 0 dumped core.
Wrote JS log to TestMachinesDisks-testAddDiskCustomPath-debian-testing-127.0.0.2-2901-FAIL.js.log
Journal extracted to TestMachinesDisks-testAddDiskCustomPath-debian-testing-127.0.0.2-2901-FAIL.log.gz
Core dumps downloaded to /work/make-checkout-workdir/TestMachinesDisks-testAddDiskCustomPath-debian-testing-127.0.0.2-2901-FAIL.core
Stopping 'libvirtd.service', but its triggering units are still active:
libvirtd-ro.socket, libvirtd.socket, libvirtd-admin.socket
Traceback (most recent call last):
  File "/work/make-checkout-workdir/test/machineslib.py", line 573, in tearDown
    super().tearDown()
    ~~~~~~~~~~~~~~~~^^
  File "/work/make-checkout-workdir/test/common/testlib.py", line 1990, in tearDown
    self.check_journal_messages()
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~^^
  File "/work/make-checkout-workdir/test/common/testlib.py", line 2253, in check_journal_messages
    raise Error(UNEXPECTED_MESSAGE + "journal messages:\n" + first)
testlib.Error: FAIL: Test completed, but found unexpected journal messages:
Process 6407 (libvirtd) of user 0 terminated abnormally with signal 11/SEGV, processing...

# Result testAddDiskCustomPath (__main__.TestMachinesDisks.testAddDiskCustomPath) failed
# 1 TEST FAILED [48s on a9ff8ad670f5]
not ok 25 /work/make-checkout-workdir/test/check-machines-disks TestMachinesDisks.testAddDiskCustomPath [ND@6]

First occurrence: 2025-04-17T03:07:10.860446+00:00 | revision 06abe7e58f6786e7f0729d2e05d379328369e302 Times recorded: 1 Latest occurrences:

2025-04-17T03:07:10.860446+00:00 | revision 06abe7e58f6786e7f0729d2e05d379328369e302

Please see https://chromedriver.chromium.org/security-considerations for suggestions on keeping ChromeDriver safe.
ChromeDriver was started successfully on port 55661.
Failed to try-restart sssd.service: Unit sssd.service not found.
bash: line 1: rpmquery: command not found
> error: Scrollbar test exception: TypeError: Cannot read properties of null (reading 'appendChild')
> warn: Failed to get current crypto policy: not-found ; falling back to /etc/crypto-policies/config
> warn: cockpit.format_{bytes,bits}[_per_sec](..., MiB, [object Object]) is deprecated.
> warn: could not execute head --bytes=16 head: error reading '/tmp/': Is a directory
Process 6404 (libvirtd) of user 0 terminated abnormally with signal 11/SEGV, processing...
Process 6404 (libvirtd) of user 0 dumped core.
Wrote JS log to TestMachinesDisks-testAddDiskCustomPath-debian-testing-127.0.0.2-2801-FAIL.js.log
Journal extracted to TestMachinesDisks-testAddDiskCustomPath-debian-testing-127.0.0.2-2801-FAIL.log.gz
Core dumps downloaded to /work/make-checkout-workdir/TestMachinesDisks-testAddDiskCustomPath-debian-testing-127.0.0.2-2801-FAIL.core
Stopping 'libvirtd.service', but its triggering units are still active:
libvirtd.socket, libvirtd-ro.socket, libvirtd-admin.socket
Traceback (most recent call last):
  File "/work/make-checkout-workdir/test/machineslib.py", line 573, in tearDown
    super().tearDown()
    ~~~~~~~~~~~~~~~~^^
  File "/work/make-checkout-workdir/test/common/testlib.py", line 1990, in tearDown
    self.check_journal_messages()
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~^^
  File "/work/make-checkout-workdir/test/common/testlib.py", line 2253, in check_journal_messages
    raise Error(UNEXPECTED_MESSAGE + "journal messages:\n" + first)
testlib.Error: FAIL: Test completed, but found unexpected journal messages:
Process 6404 (libvirtd) of user 0 terminated abnormally with signal 11/SEGV, processing...

# Result testAddDiskCustomPath (__main__.TestMachinesDisks.testAddDiskCustomPath) failed
# 1 TEST FAILED [75s on ab0b71eba10a]
not ok 25 /work/make-checkout-workdir/test/check-machines-disks TestMachinesDisks.testAddDiskCustomPath [ND@5]

First occurrence: 2025-04-21T04:10:45.571118+00:00 | revision 9488a4ae32e589056ad186969056f2e206e97040 Times recorded: 1 Latest occurrences:

2025-04-21T04:10:45.571118+00:00 | revision 9488a4ae32e589056ad186969056f2e206e97040

Please see https://chromedriver.chromium.org/security-considerations for suggestions on keeping ChromeDriver safe.
ChromeDriver was started successfully on port 37441.
Failed to try-restart sssd.service: Unit sssd.service not found.
bash: line 1: rpmquery: command not found
> error: Scrollbar test exception: TypeError: Cannot read properties of null (reading 'appendChild')
> warn: Failed to get current crypto policy: not-found ; falling back to /etc/crypto-policies/config
> warn: cockpit.format_{bytes,bits}[_per_sec](..., MiB, [object Object]) is deprecated.
> warn: could not execute head --bytes=16 head: error reading '/tmp/': Is a directory
Process 8982 (libvirtd) of user 0 terminated abnormally with signal 11/SEGV, processing...
Process 8982 (libvirtd) of user 0 dumped core.
Wrote JS log to TestMachinesDisks-testAddDiskCustomPath-debian-testing-127.0.0.2-2401-FAIL.js.log
Journal extracted to TestMachinesDisks-testAddDiskCustomPath-debian-testing-127.0.0.2-2401-FAIL.log.gz
Core dumps downloaded to /work/make-checkout-workdir/TestMachinesDisks-testAddDiskCustomPath-debian-testing-127.0.0.2-2401-FAIL.core
Stopping 'libvirtd.service', but its triggering units are still active:
libvirtd-ro.socket, libvirtd.socket, libvirtd-admin.socket
Traceback (most recent call last):
  File "/work/make-checkout-workdir/test/machineslib.py", line 573, in tearDown
    super().tearDown()
    ~~~~~~~~~~~~~~~~^^
  File "/work/make-checkout-workdir/test/common/testlib.py", line 1990, in tearDown
    self.check_journal_messages()
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~^^
  File "/work/make-checkout-workdir/test/common/testlib.py", line 2253, in check_journal_messages
    raise Error(UNEXPECTED_MESSAGE + "journal messages:\n" + first)
testlib.Error: FAIL: Test completed, but found unexpected journal messages:
Process 8982 (libvirtd) of user 0 terminated abnormally with signal 11/SEGV, processing...

# Result testAddDiskCustomPath (__main__.TestMachinesDisks.testAddDiskCustomPath) failed
# 1 TEST FAILED [44s on a61f2be07c01]
not ok 25 /work/make-checkout-workdir/test/check-machines-disks TestMachinesDisks.testAddDiskCustomPath [ND@2]

First occurrence: 2025-04-22T15:31:12.859289+00:00 | revision 8f7038b4a3cad93933426b529a8a30730ce38160 Times recorded: 1 Latest occurrences:

2025-04-22T15:31:12.859289+00:00 | revision 8f7038b4a3cad93933426b529a8a30730ce38160

Please see https://chromedriver.chromium.org/security-considerations for suggestions on keeping ChromeDriver safe.
ChromeDriver was started successfully on port 53395.
Failed to try-restart sssd.service: Unit sssd.service not found.
bash: line 1: rpmquery: command not found
> error: Scrollbar test exception: TypeError: Cannot read properties of null (reading 'appendChild')
> warn: Failed to get current crypto policy: not-found ; falling back to /etc/crypto-policies/config
> warn: cockpit.format_{bytes,bits}[_per_sec](..., MiB, [object Object]) is deprecated.
> warn: could not execute head --bytes=16 head: error reading '/tmp/': Is a directory
Process 10471 (libvirtd) of user 0 terminated abnormally with signal 11/SEGV, processing...
Process 10471 (libvirtd) of user 0 dumped core.
Wrote JS log to TestMachinesDisks-testAddDiskCustomPath-debian-testing-127.0.0.2-2201-FAIL.js.log
Journal extracted to TestMachinesDisks-testAddDiskCustomPath-debian-testing-127.0.0.2-2201-FAIL.log.gz
Core dumps downloaded to /work/make-checkout-workdir/TestMachinesDisks-testAddDiskCustomPath-debian-testing-127.0.0.2-2201-FAIL.core
Stopping 'libvirtd.service', but its triggering units are still active:
libvirtd.socket, libvirtd-ro.socket, libvirtd-admin.socket
Traceback (most recent call last):
  File "/work/make-checkout-workdir/test/machineslib.py", line 573, in tearDown
    super().tearDown()
    ~~~~~~~~~~~~~~~~^^
  File "/work/make-checkout-workdir/test/common/testlib.py", line 1990, in tearDown
    self.check_journal_messages()
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~^^
  File "/work/make-checkout-workdir/test/common/testlib.py", line 2253, in check_journal_messages
    raise Error(UNEXPECTED_MESSAGE + "journal messages:\n" + first)
testlib.Error: FAIL: Test completed, but found unexpected journal messages:
Process 10471 (libvirtd) of user 0 terminated abnormally with signal 11/SEGV, processing...

# Result testAddDiskCustomPath (__main__.TestMachinesDisks.testAddDiskCustomPath) failed
# 1 TEST FAILED [53s on 30f4ab0f607e]
not ok 25 /work/make-checkout-workdir/test/check-machines-disks TestMachinesDisks.testAddDiskCustomPath [ND@0]

First occurrence: 2025-04-22T18:32:11.911195+00:00 | revision aeb1bd51363e340d2a6d933e6507c418062bae90 Times recorded: 1 Latest occurrences:

2025-04-22T18:32:11.911195+00:00 | revision aeb1bd51363e340d2a6d933e6507c418062bae90

Please see https://chromedriver.chromium.org/security-considerations for suggestions on keeping ChromeDriver safe.
ChromeDriver was started successfully on port 54671.
Failed to try-restart sssd.service: Unit sssd.service not found.
bash: line 1: rpmquery: command not found
> error: Scrollbar test exception: TypeError: Cannot read properties of null (reading 'appendChild')
> warn: Failed to get current crypto policy: not-found ; falling back to /etc/crypto-policies/config
> warn: cockpit.format_{bytes,bits}[_per_sec](..., MiB, [object Object]) is deprecated.
> warn: could not execute head --bytes=16 head: error reading '/tmp/': Is a directory
Process 8575 (libvirtd) of user 0 terminated abnormally with signal 11/SEGV, processing...
Process 8575 (libvirtd) of user 0 dumped core.
Wrote JS log to TestMachinesDisks-testAddDiskCustomPath-debian-testing-127.0.0.2-2901-FAIL.js.log
Journal extracted to TestMachinesDisks-testAddDiskCustomPath-debian-testing-127.0.0.2-2901-FAIL.log.gz
Core dumps downloaded to /work/make-checkout-workdir/TestMachinesDisks-testAddDiskCustomPath-debian-testing-127.0.0.2-2901-FAIL.core
Stopping 'libvirtd.service', but its triggering units are still active:
libvirtd-admin.socket, libvirtd-ro.socket, libvirtd.socket
Traceback (most recent call last):
  File "/work/make-checkout-workdir/test/machineslib.py", line 573, in tearDown
    super().tearDown()
    ~~~~~~~~~~~~~~~~^^
  File "/work/make-checkout-workdir/test/common/testlib.py", line 1990, in tearDown
    self.check_journal_messages()
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~^^
  File "/work/make-checkout-workdir/test/common/testlib.py", line 2253, in check_journal_messages
    raise Error(UNEXPECTED_MESSAGE + "journal messages:\n" + first)
testlib.Error: FAIL: Test completed, but found unexpected journal messages:
Process 8575 (libvirtd) of user 0 terminated abnormally with signal 11/SEGV, processing...

# Result testAddDiskCustomPath (__main__.TestMachinesDisks.testAddDiskCustomPath) failed
# 1 TEST FAILED [46s on 33ad537ae4c1]
not ok 25 /work/make-checkout-workdir/test/check-machines-disks TestMachinesDisks.testAddDiskCustomPath [ND@6]

First occurrence: 2025-04-23T23:12:08.954774+00:00 | revision f1cd1442742453e8a4c4da8d57a22343c49f0505 Times recorded: 1 Latest occurrences:

2025-04-23T23:12:08.954774+00:00 | revision f1cd1442742453e8a4c4da8d57a22343c49f0505

Please see https://chromedriver.chromium.org/security-considerations for suggestions on keeping ChromeDriver safe.
ChromeDriver was started successfully on port 50987.
Failed to try-restart sssd.service: Unit sssd.service not found.
bash: line 1: rpmquery: command not found
> error: Scrollbar test exception: TypeError: Cannot read properties of null (reading 'appendChild')
> warn: Failed to get current crypto policy: not-found ; falling back to /etc/crypto-policies/config
> warn: cockpit.format_{bytes,bits}[_per_sec](..., MiB, [object Object]) is deprecated.
> warn: could not execute head --bytes=16 head: error reading '/tmp/': Is a directory
Process 10378 (libvirtd) of user 0 terminated abnormally with signal 11/SEGV, processing...
Process 10378 (libvirtd) of user 0 dumped core.
Wrote JS log to TestMachinesDisks-testAddDiskCustomPath-debian-testing-127.0.0.2-2201-FAIL.js.log
Journal extracted to TestMachinesDisks-testAddDiskCustomPath-debian-testing-127.0.0.2-2201-FAIL.log.gz
Core dumps downloaded to /work/make-checkout-workdir/TestMachinesDisks-testAddDiskCustomPath-debian-testing-127.0.0.2-2201-FAIL.core
Stopping 'libvirtd.service', but its triggering units are still active:
libvirtd-admin.socket, libvirtd.socket, libvirtd-ro.socket
Traceback (most recent call last):
  File "/work/make-checkout-workdir/test/machineslib.py", line 573, in tearDown
    super().tearDown()
    ~~~~~~~~~~~~~~~~^^
  File "/work/make-checkout-workdir/test/common/testlib.py", line 1990, in tearDown
    self.check_journal_messages()
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~^^
  File "/work/make-checkout-workdir/test/common/testlib.py", line 2253, in check_journal_messages
    raise Error(UNEXPECTED_MESSAGE + "journal messages:\n" + first)
testlib.Error: FAIL: Test completed, but found unexpected journal messages:
Process 10378 (libvirtd) of user 0 terminated abnormally with signal 11/SEGV, processing...

# Result testAddDiskCustomPath (__main__.TestMachinesDisks.testAddDiskCustomPath) failed
# 1 TEST FAILED [46s on bf3062d2cdd3]
not ok 25 /work/make-checkout-workdir/test/check-machines-disks TestMachinesDisks.testAddDiskCustomPath [ND@0]

First occurrence: 2025-04-24T03:11:00.838745+00:00 | revision 8789cafd606502ff5967c8c6a0191b4ebd1ff938 Times recorded: 1 Latest occurrences:

2025-04-24T03:11:00.838745+00:00 | revision 8789cafd606502ff5967c8c6a0191b4ebd1ff938

Please see https://chromedriver.chromium.org/security-considerations for suggestions on keeping ChromeDriver safe.
ChromeDriver was started successfully on port 51299.
Failed to try-restart sssd.service: Unit sssd.service not found.
bash: line 1: rpmquery: command not found
> warn: Failed to get current crypto policy: not-found ; falling back to /etc/crypto-policies/config
> error: Scrollbar test exception: TypeError: Cannot read properties of null (reading 'appendChild')
> warn: cockpit.format_{bytes,bits}[_per_sec](..., MiB, [object Object]) is deprecated.
> warn: could not execute head --bytes=16 head: error reading '/tmp/': Is a directory
Process 8800 (libvirtd) of user 0 terminated abnormally with signal 11/SEGV, processing...
Process 8800 (libvirtd) of user 0 dumped core.
Wrote JS log to TestMachinesDisks-testAddDiskCustomPath-debian-testing-127.0.0.2-2201-FAIL.js.log
Journal extracted to TestMachinesDisks-testAddDiskCustomPath-debian-testing-127.0.0.2-2201-FAIL.log.gz
Core dumps downloaded to /work/make-checkout-workdir/TestMachinesDisks-testAddDiskCustomPath-debian-testing-127.0.0.2-2201-FAIL.core
Stopping 'libvirtd.service', but its triggering units are still active:
libvirtd.socket, libvirtd-admin.socket, libvirtd-ro.socket
Traceback (most recent call last):
  File "/work/make-checkout-workdir/test/machineslib.py", line 573, in tearDown
    super().tearDown()
    ~~~~~~~~~~~~~~~~^^
  File "/work/make-checkout-workdir/test/common/testlib.py", line 1990, in tearDown
    self.check_journal_messages()
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~^^
  File "/work/make-checkout-workdir/test/common/testlib.py", line 2253, in check_journal_messages
    raise Error(UNEXPECTED_MESSAGE + "journal messages:\n" + first)
testlib.Error: FAIL: Test completed, but found unexpected journal messages:
Process 8800 (libvirtd) of user 0 terminated abnormally with signal 11/SEGV, processing...

# Result testAddDiskCustomPath (__main__.TestMachinesDisks.testAddDiskCustomPath) failed
# 1 TEST FAILED [52s on eaf3fadb24b5]
not ok 25 /work/make-checkout-workdir/test/check-machines-disks TestMachinesDisks.testAddDiskCustomPath [ND@0]

First occurrence: 2025-04-27T07:51:37.222987+00:00 | revision 993d6a54767ce67c524f3b18cdbb0b300b86835e Times recorded: 1 Latest occurrences:

2025-04-27T07:51:37.222987+00:00 | revision 993d6a54767ce67c524f3b18cdbb0b300b86835e

Only local connections are allowed.
Please see https://chromedriver.chromium.org/security-considerations for suggestions on keeping ChromeDriver safe.
ChromeDriver was started successfully on port 56651.
bash: line 1: rpmquery: command not found
> error: Scrollbar test exception: TypeError: Cannot read properties of null (reading 'appendChild')
> warn: Failed to get current crypto policy: not-found ; falling back to /etc/crypto-policies/config
> warn: cockpit.format_{bytes,bits}[_per_sec](..., MiB, [object Object]) is deprecated.
> warn: could not execute head --bytes=16 head: error reading '/tmp/': Is a directory
Process 9118 (libvirtd) of user 0 terminated abnormally with signal 11/SEGV, processing...
Process 9118 (libvirtd) of user 0 dumped core.
Wrote JS log to TestMachinesDisks-testAddDiskCustomPath-debian-testing-127.0.0.2-2801-FAIL.js.log
Journal extracted to TestMachinesDisks-testAddDiskCustomPath-debian-testing-127.0.0.2-2801-FAIL.log.gz
Core dumps downloaded to /work/make-checkout-workdir/TestMachinesDisks-testAddDiskCustomPath-debian-testing-127.0.0.2-2801-FAIL.core
Stopping 'libvirtd.service', but its triggering units are still active:
libvirtd.socket, libvirtd-ro.socket, libvirtd-admin.socket
Traceback (most recent call last):
  File "/work/make-checkout-workdir/test/machineslib.py", line 573, in tearDown
    super().tearDown()
    ~~~~~~~~~~~~~~~~^^
  File "/work/make-checkout-workdir/test/common/testlib.py", line 1994, in tearDown
    self.check_journal_messages()
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~^^
  File "/work/make-checkout-workdir/test/common/testlib.py", line 2257, in check_journal_messages
    raise Error(UNEXPECTED_MESSAGE + "journal messages:\n" + first)
testlib.Error: FAIL: Test completed, but found unexpected journal messages:
Process 9118 (libvirtd) of user 0 terminated abnormally with signal 11/SEGV, processing...

# Result testAddDiskCustomPath (__main__.TestMachinesDisks.testAddDiskCustomPath) failed
# 1 TEST FAILED [50s on 189979663e2d]
not ok 25 /work/make-checkout-workdir/test/check-machines-disks TestMachinesDisks.testAddDiskCustomPath [ND@5]

First occurrence: 2025-05-20T18:32:43.912366+00:00 | revision 5bda6b76cc9546400d8b4d184dc1c05eb4941d20 Times recorded: 1 Latest occurrences:

2025-05-20T18:32:43.912366+00:00 | revision 5bda6b76cc9546400d8b4d184dc1c05eb4941d20

Apr 16 '25 07:04 cockpituous

bots bots copied to clipboard

libvirt: segfault when attach-disk source is a directory

bots
bots copied to clipboard