Project

General

Profile

Actions

action #101301

open

unhandled output in openQA test t/24-worker-jobs.t ""exceeded MAX_JOB_TIME" and "Found base_state.json but failed..."

Added by okurz over 2 years ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
Feature requests
Target version:
Start date:
2021-10-21
Due date:
% Done:

0%

Estimated time:

Description

Observation

From
https://app.circleci.com/pipelines/github/os-autoinst/openQA/8161/workflows/e6abe712-5de1-45aa-8953-6fa32c190fb7/jobs/77185

[16:22:48] t/24-worker-jobs.t ........................................ 1/? [WARN] Job 1 stopped because it exceeded MAX_JOB_TIME
[WARN] Found poolfUai/base_state.json but failed to parse the JSON: 'false' expected, at character offset 0 (before "foo boo") at /usr/lib/perl5/vendor_perl/5.26.1/Mojo/JSON.pm line 31.

[16:22:48] t/24-worker-jobs.t ........................................ ok    20117 ms ( 0.14 usr  0.02 sys + 14.46 cusr  0.63 csys = 15.25 CPU)

Acceptance criteria

  • AC1: Test fails on any unhandled output
  • AC2: Test uses Test::Warnings ':report_warnings';
  • AC3: Test shows no unhandled output

Suggestions

  • First add use Test::Warnings ':report_warnings';
  • Find out where the unhandled output seems to come from. Seems to be in subtest "override job reason when qemu terminated with known issues by parsing autoinst-log", maybe a recent regression
  • Find out what our "best practice" regarding "fail on any unhandled output" was
  • Catch all output with e.g. combined_like and ensure there is no unhandled output
  • Optional: Add style check that all our test modules should use Test::Warnings ':report_warnings'; and maybe any check for "no unhandled output"

No data to display

Actions

Also available in: Atom PDF