Re: [PULL 00/31] various fixes (testing, plugins, gitdm)

[Peter Maydell]

On Sat, 18 Mar 2023 at 11:46, Alex Bennée <alex.bennee@linaro.org> wrote:
>
> The following changes since commit 74c581b6452394e591f13beba9fea2ec0688e2f5:
>
>   Merge tag 'trivial-branch-for-8.0-pull-request' of 
> https://gitlab.com/laurent_vivier/qemu into staging (2023-03-17 14:22:01 
> +0000)
>
> are available in the Git repository at:
>
>   https://gitlab.com/stsquad/qemu.git tags/pull-for-8.0-170323-4
>
> for you to fetch changes up to 4f2c431acd43d0aa505494229d05fa343762f272:
>
>   qtests: avoid printing comments before g_test_init() (2023-03-17
>   17:50:19 +0000)
>
> You can see my CI run on the branch here:
>
>   https://gitlab.com/stsquad/qemu/-/pipelines/810271620
>
> The failures:
>
>   FreeBSD's time out on a migration test
>   Centos8 Stream because my private runner needs more disk space
>
> ----------------------------------------------------------------
> Misc fixes for 8.0 (testing, plugins, gitdm)
>
>   - update Alpine image used for testing images
>   - include libslirp in custom runner build env
>   - update gitlab-runner recipe for CentOS
>   - update docker calls for better caching behaviour
>   - document some plugin callbacks
>   - don't use tags to define drives for lkft baseline tests
>   - fix missing clear of plugin_mem_cbs
>   - fix iotests to report individual results
>   - update the gitdm metadata for contributors
>   - avoid printing comments before g_test_init()
>

This seems to consistently fail an avocado test on the
centos-stream-8-x86_64 job:
(21/51) tests/avocado/multiprocess.py:Multiprocess.test_multiprocess_x86_64:
ERROR: ConnectError: Failed to establish session: EOFError\n Exit
code: 1\n Command: ./qemu-system-x86_64 -display none -vga none
-chardev socket,id=mon,fd=17 -mon chardev=mon,mode=control -machine
x-remote -nodefaults -device lsi53c895a,id=lsi1 -object x-remote-o...
(0.10 s)

https://gitlab.com/qemu-project/qemu/-/jobs/3962028269
https://gitlab.com/qemu-project/qemu/-/jobs/3965134190



The iotests also don't seem to pass on the OpenBSD VM after this;
which test fails varies from run to run but the common factor
is a complaint about running out of disk space:



719/774 qemu:block / io-qcow2-177
           ERROR           4.21s   exit status 1
――――――――――――――――――――――――――――――――――――― ✀  ―――――――――――――――――――――――――――――――――――――
stderr:
--- /home/qemu/qemu-test.8HLwgo/src/tests/qemu-iotests/177.out
+++ /home/qemu/qemu-test.8HLwgo/build/scratch/qcow2-file-177/177.out.bad
@@ -5,8 +5,7 @@
 wrote 134217728/134217728 bytes at offset 0
 128 MiB, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)
 Formatting 'TEST_DIR/t.IMGFMT', fmt=IMGFMT size=134217728
backing_file=TEST_DIR/t.IMGFMT.base backing_fmt=IMGFMT
-wrote 134217728/134217728 bytes at offset 0
-128 MiB, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)
+write failed: No space left on device

 == constrained alignment and max-transfer ==
 wrote 131072/131072 bytes at offset 1000
@@ -27,22 +26,27 @@
 30 MiB, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)


(etc)

and in another run

stderr:
--- /home/qemu/qemu-test.ZfU510/src/tests/qemu-iotests/040.out
+++ /home/qemu/qemu-test.ZfU510/build/scratch/qcow2-file-040/040.out.bad
@@ -1,5 +1,54 @@
-.................................................................
+................................EE...............................
+======================================================================
+ERROR: testIntermediateReadErrorReport (__main__.TestErrorHandling)
+----------------------------------------------------------------------
+Traceback (most recent call last):
+  File "/home/qemu/qemu-test.ZfU510/src/python/qemu/machine/machine.py",
line 433, in launch
+    self._launch()
+  File "/home/qemu/qemu-test.ZfU510/src/python/qemu/machine/machine.py",
line 460, in _launch
+    self._pre_launch()
+  File "/home/qemu/qemu-test.ZfU510/src/tests/qemu-iotests/iotests.py",
line 837, in _pre_launch
+    super()._pre_launch()
+  File "/home/qemu/qemu-test.ZfU510/src/python/qemu/machine/qtest.py",
line 142, in _pre_launch
+    super()._pre_launch()
+  File "/home/qemu/qemu-test.ZfU510/src/python/qemu/machine/machine.py",
line 358, in _pre_launch
+    self._qemu_log_path = os.path.join(self.log_dir, self._name + ".log")
+  File "/home/qemu/qemu-test.ZfU510/src/python/qemu/machine/machine.py",
line 905, in log_dir
+    return self.temp_dir
+  File "/home/qemu/qemu-test.ZfU510/src/python/qemu/machine/machine.py",
line 886, in temp_dir
+    self._temp_dir = tempfile.mkdtemp(prefix="qemu-machine-",
+  File "/usr/local/lib/python3.9/tempfile.py", line 363, in mkdtemp
+    _os.mkdir(file, 0o700)
+OSError: [Errno 28] No space left on device:
'/home/qemu/qemu-test.ZfU510/build/scratch/qcow2-file-040/qemu-machine-g_v0pby3'
+
+The above exception was the direct cause of the following exception:
+
+Traceback (most recent call last):
+  File "/home/qemu/qemu-test.ZfU510/src/tests/qemu-iotests/040", line
472, in setUp
+    self.vm.launch()
+  File "/home/qemu/qemu-test.ZfU510/src/python/qemu/machine/machine.py",
line 446, in launch
+    raise VMLaunchFailure(
+qemu.machine.machine.VMLaunchFailure: OSError: [Errno 28] No space
left on device:
'/home/qemu/qemu-test.ZfU510/build/scratch/qcow2-file-040/qemu-machine-g_v0pby3'
+       Command:
+       Output: None
+

The host machine (hackbox) doesn't seem to have disk space issues
so presumably the iotests want to use too much disk space for
whatever the image size is that the tests/vm infrastructure
creates ?

thanks
-- PMM