Actions
action #166670
closedcoordination #127031: [saga][epic] openQA for SUSE customers
coordination #130414: [epic] Improved code coverage in os-autoinst
[beginner][os-autoinst][CI] Unhandled output in t/27-consoles-local_xvnc.t size:S
Start date:
2024-09-11
Due date:
% Done:
0%
Estimated time:
Tags:
Description
Motivation¶
https://github.com/os-autoinst/os-autoinst/actions/runs/10636102041/job/29487175257 as well as other CI job invocations of os-autoinst show the problem of unhandled output. We want to have a clean TAP output with all output from tested application code to be captured:
3: [2024-08-30T16:38:58.763082Z] [debug] [pid:2438] Xterm PID: 2441
3: [2024-08-30T16:38:58.766070Z] [debug] [pid:2438] Xterm PID: 2442
3: [16:38:59] t/27-consoles-local_xvnc.t ............... ok 998 ms ( 0.00 usr 0.00 sys + 0.92 cusr 0.09 csys = 1.01 CPU)
Acceptance criteria¶
- AC1: No unhandled output from t/27-consoles-local_xvnc.t
Suggestions¶
- Call
prove -I. t/27-consoles-local_xvnc.tlocally 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.
Actions