mbox series

[0/2] ci: improve debuggability of I/O tests

Message ID 20220509124134.867431-1-berrange@redhat.com
Headers show
Series ci: improve debuggability of I/O tests | expand

Message

Daniel P. Berrangé May 9, 2022, 12:41 p.m. UTC 
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(-)

Comments

Kevin Wolf May 12, 2022, 10:28 a.m. UTC | #1 
Am 09.05.2022 um 14:41 hat Daniel P. Berrangé geschrieben:
> 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

Thanks, applied to the block branch.

Kevin