action #45011
open
Allow detection of known failures at the autoinst-log.txt
Added by szarate over 5 years ago.
Updated over 3 years ago.
Category:
Feature requests
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
- 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
- Related to coordination #39719: [saga][epic] Detection of "known failures" for stable tests, easy test results review and easy tracking of known issues added
- Target version set to Milestone 21+
- 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
- Related to deleted (coordination #39719: [saga][epic] Detection of "known failures" for stable tests, easy test results review and easy tracking of known issues)
- Blocks coordination #39719: [saga][epic] Detection of "known failures" for stable tests, easy test results review and easy tracking of known issues added
- Status changed from New to Workable
- Related to action #46988: [qe-core][functional] Detect known bugs from system journal added
Hi, foursixnine
It seems that #46988 was a duplicate of this ticket, but it was already picked. Could closed this as duplicate (merging content)?
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.
- Target version changed from Milestone 23 to Milestone 24
Would something like create_list_of_serial_failures in lib/known_bugs.pm be feasible?
- Status changed from Workable to In Progress
- Assignee set to dheidler
- Status changed from In Progress to Feedback
- Target version changed from Milestone 24 to Milestone 25
- Status changed from Feedback to Resolved
- 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."
- Assignee deleted (
dheidler)
- Priority changed from Normal to High
- Target version changed from Milestone 25 to Milestone 26
- 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
- Target version changed from Milestone 27 to Milestone 29
- Priority changed from High to Normal
- Target version deleted (
Milestone 29)
Not picking into tools backlog
- Subject changed from [tools] Allow detection of known failures at the autoinst-log.txt to Allow detection of known failures at the autoinst-log.txt
- Priority changed from Normal to Low
- Target version set to Ready
It's in scope for QA tools with the target version, removing additional "[tools]" tag.
- Target version changed from Ready to future
- Blocks deleted (coordination #39719: [saga][epic] Detection of "known failures" for stable tests, easy test results review and easy tracking of known issues)
- Related to coordination #39719: [saga][epic] Detection of "known failures" for stable tests, easy test results review and easy tracking of known issues added
- Related to coordination #102906: [saga][epic] Increased stability of tests with less "known failures", known incompletes handled automatically within openQA added
Also available in: Atom
PDF