Project

General

Profile

action #63065

coordination #39719: [saga][epic] Detection of "known failures" for stable tests, easy test results review and easy tracking of known issues

[gsoc] dynamic detection of error conditions from test results

Added by okurz over 1 year ago. Updated over 1 year ago.

Status:
New
Priority:
Low
Assignee:
-
Category:
Feature requests
Target version:
Start date:
2020-02-04
Due date:
% Done:

0%

Estimated time:
Difficulty:

Description

User Story

As a reviewer of failed openQA tests I want known failures of jobs regardless of the error source to be marked as such automatically to not waste time on investigating known failures

Acceptance criteria

  • AC1: If a job fails for any reason that is "known" already in the context of the current openQA instance, e.g. same failure in other jobs, the information is provided in the test details

Suggestions

  • Use data available in the database to find "failure reasons"
  • Apply innovative algorithms to learn about new failure reasons automatically, e.g. "fuzzy search", "machine learning", "artificial intelligence"
  • Provide the gathered information to the user, e.g. in the UI for job details to reference other jobs with similar failure reasons or within a build of a product

Further details

See parent ticket #39719 as well.

See https://wiki.jenkins.io/display/JENKINS/Build+Failure+Analyzer for an example. This jenkins plugin uses a "knowledge base" with jenkins instance global "known failures" defined with description and pattern matching, e.g. on "build log parsing", to mark failures as known when any log content matches existing patterns

History

#1 Updated by okurz over 1 year ago

Created issue on the openSUSE/mentoring project: https://github.com/openSUSE/mentoring/issues/121

#2 Updated by okurz over 1 year ago

  • Priority changed from Normal to Low

Also available in: Atom PDF