-
Bug
-
Resolution: Fixed
-
Minor
-
Jenkins ver. 2.89.2
Warning plugin ver. 4.64
-
-
5.0.0 (analysis-model and warnings-ng)
In log i have lines like this:
17:4>Filters\FilterBuilder.cs(229,34): warning CS0168
As a result, i see «... java.io.IOException: Failed to copy d:/workspace/ .../Filters/17:4>Filters/FilterBuilder.cs ...»,message when I try to see the warning.
This leads to a constant emergence false-new warnings (because of changed path).
Pipeline command used to build:
bat """"${tool 'msbuild 15'}\\msbuild.exe" ${params.Solution} /p:TargetFrameworkVersion=v4.5;Configuration=Debug /p:DebugType=Full /consoleloggerparameters:ErrorsOnly;NoSummary /t:Build /m"""
[JENKINS-48647] Warnings Plugin MSBuild parser wrong parse msbuild15 warnings output
C Z
created issue -
| Description |
Original:
In log i have lines like this: 17:4>Filters\FilterBuilder.cs(229,34): warning CS0168 As a result, i see «... [java.io|http://java.io/].IOException: Failed to copy d:/workspace/ .../Filters/{color:#ff0000}17:4>{color}Filters/FilterBuilder.cs ...»,message when I try to see the warning. This leads to a constant emergence false-new warnings (because of changed path). Pipeline command used to build: {code:none} bat """"${tool 'msbuild 15'}\\msbuild.exe" ${params.Solution} /p:TargetFrameworkVersion=v4.5;Configuration=Debug /p:DebugType=Full /consoleloggerparameters:ErrorsOnly;NoSummary /t:Build /m""" {code} |
New:
In log i have lines like this: {noformat} 17:4>Filters\FilterBuilder.cs(229,34): warning CS0168 {noformat} As a result, i see «... [java.io|http://java.io/].IOException: Failed to copy d:/workspace/ .../Filters/{color:#ff0000}17:4>{color}Filters/FilterBuilder.cs ...»,message when I try to see the warning. This leads to a constant emergence false-new warnings (because of changed path). Pipeline command used to build: {code:none} bat """"${tool 'msbuild 15'}\\msbuild.exe" ${params.Solution} /p:TargetFrameworkVersion=v4.5;Configuration=Debug /p:DebugType=Full /consoleloggerparameters:ErrorsOnly;NoSummary /t:Build /m""" {code} |
This is begin of log line in actual warning log. Text after "warning CS0168" just skipped.
17:4>Filters\FilterBuilder.cs(229,34): warning CS0168
What does the 17:4 stand for?
I don't know? May be it about multi threaded build. Every line in warnings log starts with \s+\d+> or \s+d+:\d+>. For example:
17:4>SqlConverter.cs(87,38): _skipped_
6>Tools\..._skipped_
Is there no absolute path possible?
There is no problem with absolute or relative path. Just about extra characters in path. In jenkins message:
Failed to copy d:/workspace/ .../Filters/17:4>Filters/FilterBuilder.cs
only "17:4>" part is wrong. Thus, it seems that the parser falsely interprets service information (17:2>) as part of path. " 6>" lines parsed correctly.
C Z
added a comment - - edited This is begin of log line in actual warning log. Text after "warning CS0168" just skipped.
17:4>Filters\FilterBuilder.cs(229,34): warning CS0168
What does the 17:4 stand for?
I don't know? May be it about multi threaded build. Every line in warnings log starts with \s+\d+> or \s+d+:\d+> . For example:
17:4>SqlConverter.cs(87,38): _skipped_
6>Tools\..._skipped_
Is there no absolute path possible?
There is no problem with absolute or relative path. Just about extra characters in path. In jenkins message:
Failed to copy d:/workspace/ .../Filters/17:4>Filters/FilterBuilder.cs
only "17:4>" part is wrong. Thus, it seems that the parser falsely interprets service information (17:2>) as part of path. " 6>" lines parsed correctly. Ok, to sum up: the current regular expression needs to be improved so that absolute paths like C:\Path\File are detected and Logging Prefixes like 17:4> are removed from the path. I think we can improve the drive detection pattern to be something like [A-Z]:\
C Z
added a comment - Like that.
Looks like this bug related to JENKINS-6709 . C Z
added a comment - I think we can improve the drive detection pattern to be something like [A-Z]:\
or fix prefix part ([^\>]+\>)(path_pattern).
Just in case I remind that this prefix i see with relative paths in msbuild log.
C Z
added a comment - I think we can improve the drive detection pattern to be something like [A-Z] :\
or fix prefix part ( [^\>] +\>)(path_pattern).
Just in case I remind that this prefix i see with relative paths in msbuild log. in MsBuildParser.java
private static final String MS_BUILD_WARNING_PATTERN = "(?:^(?:.*)Command line warning ([A-Za-z0-9]+):\\s*(.*)\\s*\\[(.*)\\])|" + ANT_TASK + "(?:(?:\\s*\\d+>)?(?:(?:(?:(.*)\\((\\d*)(?:,(\\d+))?.*\\)|.*LINK)\\s*:|(.*):)\\s*([A-z-_]*\\s?(?:[Nn]ote|[Ii]nfo|[Ww]arning|(?:fatal\\s*)?[Ee]rror))\\s*:?\\s*([A-Za-z0-9]+)\\s*:\\s(?:\\s*([A-Za-z0-9.]+)\\s*:)?\\s*(.*?)(?: \\[([^\\]]*)[/\\\\][^\\]\\\\]+\\])?" + "|(.*)\\s*:.*error\\s*(LNK[0-9]+):\\s*(.*)))$";
this part
(?:\\s*\\d+>)
maybe need to change to (?:s*[^>]+>)
or
"(?:\\s*(?:\\d+|\\d+:\\d+)>)"
C Z
added a comment - - edited in MsBuildParser.java
private static final String MS_BUILD_WARNING_PATTERN = "(?:^(?:.*)Command line warning ([A-Za-z0-9]+):\\s*(.*)\\s*\\[(.*)\\])|"
+ ANT_TASK + "(?:(?:\\s*\\d+>)?(?:(?:(?:(.*)\\((\\d*)(?:,(\\d+))?.*\\)|.*LINK)\\s*:|(.*):)\\s*([A-z-_]*\\s?(?:[Nn]ote|[Ii]nfo|[Ww]arning|(?:fatal\\s*)?[Ee]rror))\\s*:?\\s*([A-Za-z0-9]+)\\s*:\\s(?:\\s*([A-Za-z0-9.]+)\\s*:)?\\s*(.*?)(?: \\[([^\\]]*)[/\\\\][^\\]\\\\]+\\])?"
+ "|(.*)\\s*:.*error\\s*(LNK[0-9]+):\\s*(.*)))$" ;
this part
(?:\\s*\\d+>)
maybe need to change to (?:s* [^>] +>)
or
"(?:\\s*(?:\\d+|\\d+:\\d+)>)"
Is this the exact log message? What does the 17:4 stand for? Is there no absolute path possible?