action #178117
closed
coordination #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 size:S
Added by okurz 3 months ago.
Updated 27 days ago.
Category:
Regressions/Crashes
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: Unhandled output from any openQA test called with prove is prevented by automatic checks
AC2: Other related projects have according improvements planned or implemented
-
AC3: Output of the tests should still be immediate and not printed with delay
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
- Provide a regex representing a line of valid prove output to verify "no output"
- Copied from action #178111: [beginner][openQA][CI] Unhandled output in t/05-scheduler-restart-and-duplicate.t added
- Target version changed from Ready to Tools - Next
- Target version changed from Tools - Next to Ready
- Subject changed from [openQA][CI] Prevent unhandled output in prove test calls with automatic checks to [openQA][CI] Prevent unhandled output in prove test calls with automatic checks size:S
- Description updated (diff)
- Status changed from New to Workable
- Status changed from Workable to In Progress
- Status changed from In Progress to Feedback
I made AC1 clearer, that it is not about one single occurrence of unhandled output.
- Description updated (diff)
Actually now I made the description clearer. Before it got lost because of conflicting issue commenting.
- Status changed from Feedback to In Progress
- Description updated (diff)
- Status changed from In Progress to Blocked
- Status changed from Blocked to Workable
Please keep in mind that Blocked is for external dependencies where we have a ticket to block on, not for open questions you need help answering
- Status changed from Workable to Feedback
- Status changed from Feedback to In Progress
- Status changed from In Progress to Feedback
- Status changed from Feedback to Resolved
- Status changed from Resolved to In Progress
I think I got confused between pr, sorry!
About the AC2, I've take a look into os-autoinst/os-autoinst, but it's more complex to work with and edit like the way I do for os-autoinst/openqa.
- Description updated (diff)
As discussed during the dev daily today I'll move the AC2 into a new ticket because it is not feasible to complete it today due to online meetings.
- Description updated (diff)
- Description updated (diff)
- Copied to action #181358: [openQA][CI] Prevent unhandled output in prove test calls with automatic checks in os-autoinst added
- Status changed from In Progress to Feedback
- Status changed from Feedback to Resolved
- Copied to action #181760: [sporadic][openQA][CI] unhandled output in t/full-stack.t "Use of uninitialized value in numeric ne (!=) lib/OpenQA/Worker/Job.pm line 770" added
Also available in: Atom
PDF