action #63065


coordination #102906: [saga][epic] Increased stability of tests with less "known failures", known incompletes handled automatically within openQA

coordination #102912: [epic] Simplify investigation of job failures - 2nd

[gsoc] dynamic detection of error conditions from test results

Added by okurz over 4 years ago. Updated about 1 year ago.

Feature requests
Target version:
Start date:
Due date:
% Done:


Estimated time:


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


  • 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 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

Actions #1

Updated by okurz over 4 years ago

Created issue on the openSUSE/mentoring project:

Actions #2

Updated by okurz about 4 years ago

  • Priority changed from Normal to Low
Actions #3

Updated by okurz over 2 years ago

  • Parent task changed from #39719 to #102912
Actions #4

Updated by okurz about 1 year ago

  • Status changed from New to Resolved
  • Assignee set to okurz was completed, see for a report. We don't have the solution enabled in our production environments but the ticket in the current state also wouldn't really help so we would need to reconsider in a new story anyway.


Also available in: Atom PDF