Project

General

Profile

action #45011

[tools] Allow detection of known failures at the autoinst-log.txt

Added by szarate over 1 year ago. Updated 6 months ago.

Status:
Workable
Priority:
Normal
Assignee:
-
Category:
Feature requests
Target version:
-
Start date:
2018-12-11
Due date:
% Done:

0%

Estimated time:
Difficulty:
Duration:

Description

PRs https://github.com/os-autoinst/os-autoinst/pull/1014 and https://github.com/os-autoinst/os-autoinst/pull/932 laid the fundation to process failures that were happening outside the test scope, but they don't cover autoinst-log.txt for example.

I created https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/6315 as a starting point when I stumbled across the problem, time to put it into a real ticket.

User Story

As an Test engineer I would like to have the capability of detecting problems in the worker host or os-autoinst so that the test can be cancelled if necesary

AC:

  • Provide a mechanism to match on regex in autoinst-log.txt based on patterns defined in the test distribution (preferably not in the main.pm or test suites per se, but it's own domain)
  • Provide patterns defined in os-autoinst for backend specific stuff, e.g. the "key event queue full"-thingy -> look for that string in os-autoinst for existing code to handle that
  • Enhance existing documentation

Related issues

Related to openQA Tests - action #46988: [functional][u] Detect known bugs from system journalNew2018-04-16

Related to openQA Project - action #52235: isotovideo -d brokenResolved2019-05-28

Blocks openQA Project - action #39719: [saga][epic] Detect "known failures" and mark jobs as suchBlocked2018-04-162020-06-09

History

#1 Updated by szarate over 1 year ago

  • Subject changed from [tools]][u] Allow detection of known failures at the autoinst-log.txt to [tools][u] Allow detection of known failures at the autoinst-log.txt

#2 Updated by szarate over 1 year ago

  • Related to action #39719: [saga][epic] Detect "known failures" and mark jobs as such added

#3 Updated by szarate over 1 year ago

  • Target version set to Milestone 21+

#4 Updated by okurz over 1 year ago

  • Subject changed from [tools][u] Allow detection of known failures at the autoinst-log.txt to [tools][functional][u] Allow detection of known failures at the autoinst-log.txt
  • Target version changed from Milestone 21+ to Milestone 23

#5 Updated by agraul over 1 year ago

  • Related to deleted (action #39719: [saga][epic] Detect "known failures" and mark jobs as such)

#6 Updated by agraul over 1 year ago

  • Blocks action #39719: [saga][epic] Detect "known failures" and mark jobs as such added

#7 Updated by szarate over 1 year ago

  • Status changed from New to Workable

#8 Updated by okurz about 1 year ago

  • Related to action #46988: [functional][u] Detect known bugs from system journal added

#9 Updated by SLindoMansilla about 1 year ago

Hi, foursixnine

It seems that #46988 was a duplicate of this ticket, but it was already picked. Could closed this as duplicate (merging content)?

#10 Updated by szarate about 1 year ago

Sergio, that one talks about journal logs, which come from the SUT, this ticket talks about isotovideo generated logs (backend), which would be an enhancement, and would require different processing on autoinst-log.txt as the messages are different, and do not come from the serial console of the sut.

#11 Updated by mgriessmeier about 1 year ago

  • Target version changed from Milestone 23 to Milestone 24

moving to M24

#12 Updated by dheidler about 1 year ago

Would something like create_list_of_serial_failures in lib/known_bugs.pm be feasible?

#13 Updated by dheidler about 1 year ago

  • Status changed from Workable to In Progress
  • Assignee set to dheidler

#14 Updated by dheidler about 1 year ago

  • Status changed from In Progress to Feedback

#15 Updated by mgriessmeier about 1 year ago

  • Target version changed from Milestone 24 to Milestone 25

#16 Updated by szarate 12 months ago

  • Status changed from Feedback to Resolved

#17 Updated by okurz 12 months ago

#18 Updated by okurz 12 months ago

  • Status changed from Resolved to Workable

There was some fallout, see #52235 and #52247 . I guess we should continue here.

As coolo suggested:

"there is a reason the worker writes this file - because we add additional infos to it. […] Still having 2 processes writing the same file is very dangerous. It is just stupid to open a file and then start another process to write to it. I veto this insanity - because in a couple of days you guys will file tickets for truncated log files and complain. I repeat what I said: if isotovideo wants to catch log output, this should be a Mojo::Log subclass that does not write. And leave autoinst-log.txt alone."

#19 Updated by dheidler 11 months ago

  • Assignee deleted (dheidler)

#20 Updated by mgriessmeier 11 months ago

  • Priority changed from Normal to High
  • Target version changed from Milestone 25 to Milestone 26

#21 Updated by mgriessmeier 10 months ago

  • Subject changed from [tools][functional][u] Allow detection of known failures at the autoinst-log.txt to [tools] Allow detection of known failures at the autoinst-log.txt
  • Target version changed from Milestone 26 to Milestone 27

In the u-team we don't have the resources to look into this right now, since it apparently requires a lot of effort to check backend specific stuff
feel free to discuss with me in person - for now removing u-tag

#22 Updated by mgriessmeier 9 months ago

  • Target version changed from Milestone 27 to Milestone 29

#23 Updated by coolo 8 months ago

  • Priority changed from High to Normal
  • Target version deleted (Milestone 29)

Not picking into tools backlog

#24 Updated by okurz 6 months ago

My approach, focussed on incompletes, are based on the scripts openqa-monitor-incompletes and openqa-label-known-issues triggered in a gitlab CI pipeline in https://gitlab.suse.de/openqa/auto-review/pipelines

Also available in: Atom PDF