QA » openQA Project

Motivation¶

We want to have a clean TAP output with all output from tested application code to be captured. In https://github.com/os-autoinst/os-autoinst/actions/runs/3876337077/jobs/6610044151#step:3:618 we see unhandled output:

7: [2023-01-09T17:53:01.568078Z] [debug] [pid:2148] >>> basetest::verify_sound_image: found foundneedle, similarity 100.00 @ 1/2
7: [2023-01-09T17:53:01.573017Z] [debug] [pid:2148] >>> basetest::verify_sound_image: failed to find /opt/t/data/frame2.ppm
7: [2023-01-09T17:53:01.577323Z] [debug] [pid:2148] >>> basetest::verify_sound_image: failed to find /opt/t/data/frame2.ppm
7: [2023-01-09T17:53:01.582419Z] [info] [pid:2148] ::: basetest::runtest: # Test died: test failure at ./t/17-basetest.t line 519.
7:   
7: [2023-01-09T17:53:01.583510Z] [debug] [pid:2148] ignoring previously logged failure via developer mode
7: [2023-01-09T17:53:01.584096Z] [debug] [pid:2148] ||| finished basetest unknown (runtime: 0 s)
7: [17:53:02] ./t/17-basetest.t .......................... ok     1849 ms ( 0.01 usr  0.00 sys +  1.80 cusr  0.14 csys =  1.95 CPU)
7: [2023-01-09T17:53:03.661582Z] [warn] [pid:2151] !!! backend::qemu::_set_graphics_backend: QEMU_OVERRIDE_VIDEO_DEVICE_AARCH64 is deprecated, please set QEMU_VIDEO_DEVICE=VGA instead
7: [2023-01-09T17:53:03.662028Z] [warn] [pid:2151] !!! backend::qemu::_set_graphics_backend: QEMUVGA is deprecated, please set QEMU_VIDEO_DEVICE
7: [2023-01-09T17:53:03.662428Z] [warn] [pid:2151] !!! backend::qemu::_set_graphics_backend: QEMUVGA is deprecated, please set QEMU_VIDEO_DEVICE
7: [2023-01-09T17:53:03.662817Z] [warn] [pid:2151] !!! backend::qemu::_set_graphics_backend: Both QEMUVGA and QEMU_VIDEO_DEVICE set, ignoring deprecated QEMUVGA!
7: [17:53:06] ./t/18-backend-qemu.t ...................... ok     4308 ms ( 0.02 usr  0.00 sys +  3.85 cusr  0.47 csys =  4.34 CPU)

Acceptance criteria¶

• AC1: No unhandled output from t/18-backend-qemu.t

Suggestions¶

• Call prove -I. t/18-backend-qemu.t locally to reproduce
• Check which part of the code triggers the output, e.g. by checking the output of prove -v ...
• Surround calls with according output capture code as we already have in many other cases, likely even in the same test module.