Project

General

Profile

Actions

action #166667

closed

coordination #127031: [saga][epic] openQA for SUSE customers

coordination #130414: [epic] Improved code coverage in os-autoinst

[beginner][os-autoinst][CI] Unhandled output in t/26-video_stream.t size:S

Added by okurz 2 months ago. Updated 8 days ago.

Status:
Resolved
Priority:
Low
Assignee:
Category:
Regressions/Crashes
Target version:
Start date:
2024-09-11
Due date:
% Done:

0%

Estimated time:

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/30 16:38:57 socat[2428] E write(1, 0x55babb48d000, 8192): Broken pipe
3: 2024/08/30 16:38:57 socat[2431] E write(1, 0x55722d72a000, 8192): Broken pipe
3: 2024/08/30 16:38:57 socat[2434] E write(1, 0x55dcb0e99000, 8192): Broken pipe

Acceptance criteria

  • AC1: No unhandled output from t/26-video_stream.t

Suggestions

  • Call prove -I. t/26-video_stream.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.

Related issues 2 (1 open1 closed)

Copied from openQA Project - action #166664: [beginner][os-autoinst][CI] Unhandled output in t/23-baseclass.t size:SResolvedjbaier_cz2024-09-11

Actions
Copied to openQA Project - action #166670: [beginner][os-autoinst][CI] Unhandled output in t/27-consoles-local_xvnc.t size:SWorkable2024-09-11

Actions
Actions

Also available in: Atom PDF