coordination #39719: [saga][epic] Detect "known failures" and mark jobs as such to make tests more stable, reviewing test results and tracking known issues easier
[gsoc] dynamic detection of error conditions from test results
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
- 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
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