ci: improve debuggability of I/O tests
Status from this message: Thanks, applied to the block branch.
Get series with b4
b4 am [email protected]Versions newest first
Patches in v1 Applied
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/2 | tests/qemu-iotests: print intent to run a test in TAP modetests/ | +3 | 1 reply | |
| 2/2 | .gitlab-ci.d: export meson testlog.txt as an artifact.gitlab-ci.d/ | +10 | 2 replies |
Reviews trailers per patch
All 2 patches have a Reviewed-by or Acked-by.
| Patch | Thomas Huth | Philippe Mathieu-Daudé |
|---|---|---|
| 1/2 | R-b | |
| 2/2 | R-b | R-b |
Trailers given in replies are filled; those carried in the patches from earlier versions are outlined with dashes.
Cover letter [PATCH 0/2] ci: improve debuggability of I/O tests
Currently with the TAP harness we see essentially no useful information about the I/O tests execution. To pick a random job:
https://gitlab.com/qemu-project/qemu/-/jobs/2429330423
All that we get is this:
184/204 qemu:block / qemu-iotests qcow2 OK 309.10s 116 subtests passed
The full details are in a testlog.txt file that isn't accessible. This series publishes that as an artifact. It further tweaks the TAP runner to print out when it is about to run a test, so we get a record of what was running, if the test harness gets terminated abnormally/prematurely
Daniel P. Berrangé (2):
tests/qemu-iotests: print intent to run a test in TAP mode .gitlab-ci.d: export meson testlog.txt as an artifact
.gitlab-ci.d/buildtest-template.yml | 12 ++++++++++-- tests/qemu-iotests/testrunner.py | 3 +++ 2 files changed, 13 insertions(+), 2 deletions(-)
Signature · 1 line
2.35.1