action #46988
openopenQA Project - coordination #102906: [saga][epic] Increased stability of tests with less "known failures", known incompletes handled automatically within openQA
openQA Project - coordination #102912: [epic] Simplify investigation of job failures - 2nd
[qe-core][functional] Detect known bugs from system journal
Added by okurz over 5 years ago. Updated about 2 months ago.
0%
Description
Motivation¶
See parent ticket #39719 . As test reviewers we want to have less work to label jobs for known issues that can be detected from the system journal which we also upload
Acceptance criteria¶
- AC1: We have an easy way to reference bugs as soft-failures by looking at matching patterns in the system journal
Suggestions¶
- Take a look into the file
lib/known_bugs.pmas introduced with 4fac2c92c - Extend pattern matching functionality to look into the system journal as well, maybe just use a matching pattern in the same file but used in the generic post_fail_hook that uploads the systemd journal, e.g. in lib/opensusebasetest.pm:problem_detection
- Use example https://openqa.suse.de/tests/2429429#step/firefox/5 for detecting the firefox segfaulting on ppc64le
- Use force_soft_failure
Updated by okurz over 5 years ago
- Project changed from openQA Project to openQA Tests
- Category set to Enhancement to existing tests
- Status changed from New to Workable
- Priority changed from Normal to High
- Target version set to Milestone 23
Updated by okurz about 5 years ago
- Due date set to 2019-03-12
Setting later due-date to push off reminders in parent ticket.
Updated by jorauch about 5 years ago
- Status changed from Workable to In Progress
- Assignee set to jorauch
Taking a look
Updated by jorauch about 5 years ago
We should add a function to scan journalctl and call that in the post_fail_hook.
Updated by jorauch about 5 years ago
We could use zluos idea of printing it to the serial log and reuse the existing serial scan for patterns
https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/6702
Updated by jorauch about 5 years ago
- Status changed from In Progress to Workable
Actually no progress so far due to other tasks
Updated by jorauch about 5 years ago
Proof of concept:
http://pinky.arch.suse.de/tests/66#step/prepare_test_data/24
Injected a test error to known_bugs and a "echo 'test_bug'" to prepare_test_data
Updated by jorauch about 5 years ago
- Status changed from Workable to In Progress
Updated by jorauch about 5 years ago
- Status changed from In Progress to Workable
Updated by jorauch about 5 years ago
- Assignee deleted (
jorauch)
Unassigning as discussed in the daily
Updated by okurz about 5 years ago
- Related to action #45011: Allow detection of known failures at the autoinst-log.txt added
Updated by okurz about 5 years ago
- Due date changed from 2019-03-12 to 2019-06-30
Updated by dheidler about 5 years ago
- Status changed from Workable to In Progress
Updated by dheidler about 5 years ago
Fix force_soft_failure: https://github.com/os-autoinst/os-autoinst/pull/1136
Updated by dheidler about 5 years ago
- Status changed from In Progress to Feedback
Updated by mgriessmeier about 5 years ago
- Target version changed from Milestone 23 to Milestone 24
moving to M24
Updated by SLindoMansilla about 5 years ago
- Status changed from Feedback to Workable
Updated by SLindoMansilla about 5 years ago
- Status changed from Workable to Feedback
This should be picked up for grooming to define the specification of force_soft_failure. (okurz has to be present)
(I tried to change the status to new, but it is not shown)
Updated by mgriessmeier almost 5 years ago
- Target version changed from Milestone 24 to Milestone 25
Updated by szarate almost 5 years ago
- Status changed from Feedback to New
- Assignee deleted (
dheidler)
We can discuss this with Oliver sometime this week...
Updated by szarate almost 5 years ago
- Status changed from New to Feedback
- Assignee set to SLindoMansilla
Assigning to Sergio until he comes back
Updated by riafarov almost 5 years ago
- Due date changed from 2019-06-30 to 2019-08-06
Sorry for the noise, I've set due date to some time in future in order not to receive e-mail notifications about tickets with due dates (get them from parent epic I am tracking).
Updated by mgriessmeier almost 5 years ago
- Target version changed from Milestone 25 to Milestone 26
Updated by SLindoMansilla almost 5 years ago
- Priority changed from Normal to Urgent
To discuss on grooming
Updated by riafarov over 4 years ago
- Due date changed from 2019-08-06 to 2019-12-31
Same as before, fixing due date not to receive emails about tickets with due dates.
Updated by mgriessmeier over 4 years ago
- Status changed from Feedback to New
- Target version changed from Milestone 26 to Milestone 27
Updated by mgriessmeier over 4 years ago
- Target version changed from Milestone 27 to Milestone 28
Updated by SLindoMansilla over 4 years ago
- Status changed from New to Workable
- Priority changed from Urgent to Normal
- Estimated time set to 42.00 h
Santi will provide the bug number.
This PR is needed before start working on this: https://github.com/os-autoinst/os-autoinst/pull/1136
Updated by mgriessmeier over 4 years ago
- Target version changed from Milestone 28 to Milestone 30
needs to be discussed offline
Updated by okurz over 4 years ago
- Due date changed from 2019-12-31 to 2020-12-31
Updated by SLindoMansilla about 4 years ago
- Status changed from Workable to New
- Assignee set to SLindoMansilla
Maybe we can use an observer in the test distribution side.
Updated by szarate almost 4 years ago
- Start date set to 2018-04-16
due to changes in a related task: #46988
Updated by szarate almost 4 years ago
- Assignee deleted (
SLindoMansilla) - Start date deleted (
2019-02-01) - Estimated time deleted (
42.00 h)
SLindoMansilla wrote:
Maybe we can use an observer in the test distribution side.
An observer pattern could be introduced on the test distribution side, but also piping the journal to some serial console aswell could help here
Unasigning Sergio, (and removing estimated time) perhaps it can be picked up or groomed later on even more
Updated by szarate over 3 years ago
- Related to action #60992: [qe-core][functional][sporadic] generic problem with select_console / workqueue lockup message added
Updated by tjyrinki_suse over 3 years ago
- Subject changed from [functional][u] Detect known bugs from system journal to [qe-core][functional] Detect known bugs from system journal
Updated by okurz over 2 years ago
I came to this ticket due to periodically reviewing tickets as described on https://progress.opensuse.org/projects/openqatests/wiki#How-we-work-on-tickets
This ticket was set to "Normal" priority but was not updated within the SLO period for "Normal" tickets (365 days) as described on https://progress.opensuse.org/projects/openqatests/wiki/Wiki#SLOs-service-level-objectives
First reminder: Please consider picking up this ticket within the next 365 days or just set the ticket to the next lower priority of "Low" (no SLO related time period).
Updated by slo-gin over 1 year ago
This ticket was set to Normal priority but was not updated within the SLO period. Please consider picking up this ticket or just set the ticket to the next lower priority.
Updated by slo-gin about 2 months ago
This ticket was set to Normal priority but was not updated within the SLO period. Please consider picking up this ticket or just set the ticket to the next lower priority.