Some subtests have over-optimistic timeouts and time out on the s390 runner
The s390 runner is a VM on a shared system, so if the host is heavily loaded our CI jobs can run slowly there. When they do, the CI job tends to fail because some subtest or another has timed out. We should raise those timeouts. Here is a list of subtests which have failed for timeout on that machine:
https://gitlab.com/qemu-project/qemu/-/jobs/6136064415:
224/856 qemu:unit / test-replication TIMEOUT 62.70s 10 subtests passed
338/856 qemu:qtest+qtest-i386 / qtest-i386/ahci-test TIMEOUT 60.20s killed by signal 15 SIGTERM
552/856 qemu:qtest+qtest-x86_64 / qtest-x86_64/ahci-test TIMEOUT 60.33s killed by signal 15 SIGTERM
735/856 qemu:block / io-qcow2-040 TIMEOUT 180.09s killed by signal 15 SIGTERM
737/856 qemu:block / io-qcow2-041 TIMEOUT 180.15s killed by signal 15 SIGTERM
856/856 qemu:block / io-qcow2-271 TIMEOUT 180.21s killed by signal 15 SIGTERM
https://gitlab.com/qemu-project/qemu/-/jobs/6150109382:
227/856 qemu:unit / test-replication TIMEOUT 62.75s 10 subtests passed
571/856 qemu:qtest+qtest-x86_64 / qtest-x86_64/ahci-test TIMEOUT 60.11s killed by signal 15 SIGTERM
750/856 qemu:block / io-qcow2-040 TIMEOUT 180.02s killed by signal 15 SIGTERM
755/856 qemu:block / io-qcow2-041 TIMEOUT 180.03s killed by signal 15 SIGTERM
https://gitlab.com/qemu-project/qemu/-/jobs/6149302004:
228/856 qemu:unit / test-replication TIMEOUT 62.53s 9 subtests passed
559/856 qemu:qtest+qtest-x86_64 / qtest-x86_64/ahci-test TIMEOUT 60.23s killed by signal 15 SIGTERM
742/856 qemu:block / io-qcow2-040 TIMEOUT 180.05s killed by signal 15 SIGTERM
743/856 qemu:block / io-qcow2-041 TIMEOUT 180.18s killed by signal 15 SIGTERM
https://gitlab.com/qemu-project/qemu/-/jobs/6159694650
783/857 qemu:block / io-qcow2-copy-before-write ERROR 15.94s exit status 1
>>> MALLOC_PERTURB_=59 PYTHON=/home/gitlab-runner/builds/FLaZkdt1/0/qemu-project/qemu/build/pyvenv/bin/python3 /home/gitlab-runner/builds/FLaZkdt1/0/qemu-project/qemu/build/pyvenv/bin/python3 /home/gitlab-runner/builds/FLaZkdt1/0/qemu-project/qemu/build/../tests/qemu-iotests/check -tap -qcow2 copy-before-write --source-dir /home/gitlab-runner/builds/FLaZkdt1/0/qemu-project/qemu/tests/qemu-iotests --build-dir /home/gitlab-runner/builds/FLaZkdt1/0/qemu-project/qemu/build/tests/qemu-iotests
――――――――――――――――――――――――――――――――――――― ✀ ―――――――――――――――――――――――――――――――――――――
stderr:
--- /home/gitlab-runner/builds/FLaZkdt1/0/qemu-project/qemu/tests/qemu-iotests/tests/copy-before-write.out
+++ /home/gitlab-runner/builds/FLaZkdt1/0/qemu-project/qemu/build/scratch/qcow2-file-copy-before-write/copy-before-write.out.bad
@@ -1,5 +1,21 @@
-....
+..F.
+======================================================================
+FAIL: test_timeout_break_guest (__main__.TestCbwError)
+----------------------------------------------------------------------
+Traceback (most recent call last):
+ File "/home/gitlab-runner/builds/FLaZkdt1/0/qemu-project/qemu/tests/qemu-iotests/tests/copy-before-write", line 194, in test_timeout_break_guest
+ self.assertEqual(log, """\
+AssertionError: 'wrot[90 chars])\nwrote 524288/524288 bytes at offset 524288\[151 chars]c)\n' != 'wrot[90 chars])\nwrite failed: Connection timed out\nread 10[85 chars]c)\n'
+ wrote 524288/524288 bytes at offset 0
+ 512 KiB, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)
++ write failed: Connection timed out
+- wrote 524288/524288 bytes at offset 524288
+- 512 KiB, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)
+ read 1048576/1048576 bytes at offset 0
+ 1 MiB, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)
+
+
----------------------------------------------------------------------
Ran 4 tests
-OK
+FAILED (failures=1)
(test program exited with status code 1)
――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――
Edited by Peter Maydell