Actions
action #178117
opencoordination #127031: [saga][epic] openQA for SUSE customers
coordination #165393: [epic] Improved code coverage in openQA
[openQA][CI] Prevent unhandled output in prove test calls with automatic checks
Start date:
2025-03-01
Due date:
% Done:
0%
Estimated time:
Tags:
Description
Motivation¶
https://app.circleci.com/pipelines/gh/os-autoinst/openQA/16015/workflows/93b25d9c-129a-40d0-8dec-82b2390fb56b/jobs/154230 shows a problem of unhandled output. We want to have a clean TAP output with all output from tested application code to be captured:
[23:50:36] t/05-scheduler-restart-and-duplicate.t .................... 22/? # {
# '100006' => 100012,
# '100008' => 100013,
# '100009' => 100014,
# '100010' => 100015
# }
[23:50:36] t/05-scheduler-restart-and-duplicate.t .................... ok 14366 ms ( 0.04 usr 0.01 sys + 13.61 cusr 0.37 csys = 14.03 CPU)
[
Acceptance criteria¶
- AC1: No unhandled output from any openQA test called with prove
- AC2: Other related projects have according improvements planned or implemented
Suggestions¶
- Research how others might achieve it already or use our own check of logs or a "prove wrapper"
- After that works for openQA fix it or report in tickets for related projects
Updated by okurz about 1 month ago
- Copied from action #178111: [beginner][openQA][CI] Unhandled output in t/05-scheduler-restart-and-duplicate.t added
Actions