Actions
action #178111
closedcoordination #127031: [saga][epic] openQA for SUSE customers
coordination #165393: [epic] Improved code coverage in openQA
[beginner][openQA][CI] Unhandled output in t/05-scheduler-restart-and-duplicate.t
Start date:
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 t/05-scheduler-restart-and-duplicate.t
Suggestions¶
- Call
make test KEEP_DB=1 TESTS=t/05-scheduler-restart-and-duplicate.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.
Actions