add patterns to extract various warning pattern#509
Draft
dirk-thomas wants to merge 1 commit intomasterfrom
Draft
add patterns to extract various warning pattern#509dirk-thomas wants to merge 1 commit intomasterfrom
dirk-thomas wants to merge 1 commit intomasterfrom
Conversation
Signed-off-by: Dirk Thomas <dirk-thomas@users.noreply.github.com>
This was referenced Aug 27, 2020
Member
Author
|
Tickets which need to be resolved before this can be merged without resulting in job state regressions:
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fixes #418.
Atm various kind of warnings are present in the job output (specifically the
stderrlog of thetestinvocation) but being ignored.This patch adds multiple patterns to each job to match different kinds of warnings:
foonathanpytestwarnings - with/without a reference to a specific file:linenoThese pattern cover all the cases mentioned in #447 (comment):
In order to work the Jenkins master needs to define the following custom Groovy parsers in
io.jenkins.plugins.analysis.warnings.groovy.ParserConfiguration.xml:Before this change can be merged the reported errors should be addressed to not regress the job states: