[JENKINS-55390] No issues found when parsing Error-Prone output from console log during maven build

Type: Bug
Resolution: Cannot Reproduce
Priority: Minor
Component/s: warnings-ng-plugin
Labels:
None
Environment:
Jenkins: 2.156
warnings-ng-plugin: 1.0.1
error-prone: 2.3.2
plexus-compiler: 2.8.4
maven: 3.5.4
java: 1.8.0_191

Similar Issues:
Powered by SuggestiMate

Show

Maven build using Error Prone compiler completes with:

channel stopped
[Error Prone] Sleeping for 5 seconds due to JENKINS-32191...
[Error Prone] Parsing console log (workspace: '/pathtoworkspace/workspace/xxx')
[Error Prone] Attaching ResultAction with ID 'error-prone' to run 'xxx #1411'.
[Error Prone] Using reference build 'xxx #1410' to compute new, fixed, and outstanding issues
[Error Prone] Issues delta (vs. reference build): outstanding: 0, new: 0, fixed: 0
[Error Prone] Evaluating quality gates
[Error Prone] -> All quality gates have been passed
[Error Prone] Health report is disabled - skipping
[Error Prone] Created analysis result for 0 issues (found 0 new issues, fixed 0 issues)
Finished: SUCCESS

Inspection of job's log shows entries like the example below:

[pool-1-thread-3 for channel id=36910] WARNING org.apache.maven.plugin.compiler.CompilerMojo - /pathtoworkspace/workspace/xxx/xxx-module/src/main/java/a/path/SomeClass.java:[209,74] [DefaultCharset] Implicit use of the platform default charset, which can result in differing behaviour between JVM executions or incorrect behavior if the encoding of the data source doesn't match expectations.
    (see https://errorprone.info/bugpattern/DefaultCharset)
  Did you mean '+ Base64.encodeBase64String(aString.getBytes(UTF_8)) + "')");' or '+ Base64.encodeBase64String(aString.getBytes(Charset.defaultCharset())) + "')");'?

It seems that the warnings are not detected (due to the 'pool-1-thread' or 'org.apache.maven.plugin.compiler.CompilerMojo' stuff?) from console log.

A local build (using the same maven, java and error-prone version) show the warning in the form below:

[WARNING] <pathtoworkspace>/SomeClass.java:[209,74] [DefaultCharset] Implicit use of the platform default charset, which can result in differing behaviour between JVM executions or incorrect behavior if the encoding of the data source doesn't match expectations.
    (see https://errorprone.info/bugpattern/DefaultCharset)
  Did you mean '+ Base64.encodeBase64String(aString.getBytes(UTF_8)) + "')");' or '+ Base64.encodeBase64String(aString.getBytes(Charset.defaultCharset())) + "')");'?

So there is obviously a difference in console-log formating.

is related to

JENKINS-72976 Extra logging added to console log on Maven builds and prevent Error-Prone parsing

Closed

Marco Rothe created issue - 2019-01-03 12:45

Marco Rothe made changes - 2019-01-03 12:47

Environment

Original: Jenkins: 2.156
warnings-ng-plugin: 1.0.1
ecj: 3.16.0, 3.15.1
plexus-compiler: 2.8.5
maven: 3.6.0
java: 1.8.0_191

New: Jenkins: 2.156
warnings-ng-plugin: 1.0.1
error-prone: 2.3.2
plexus-compiler: 2.8.4
maven: 3.5.4
java: 1.8.0_191

Marco Rothe made changes - 2019-01-03 12:54

Description

Original: Maven build using ECJ completes with:
{noformat}
channel stopped
[Eclipse ECJ] Sleeping for 5 seconds due to ~~JENKINS-32191~~...
[Eclipse ECJ] Parsing console log (workspace: '/home/jenkins-agent/agent-1/workspace/xxx')
[Eclipse ECJ] Attaching ResultAction with ID 'eclipse' to run 'xxx #10'.
[Eclipse ECJ] Using reference build 'xxx #9' to compute new, fixed, and outstanding issues
[Eclipse ECJ] Issues delta (vs. reference build): outstanding: 0, new: 0, fixed: 0
[Eclipse ECJ] No quality gates have been set - skipping
[Eclipse ECJ] Health report is disabled - skipping
[Eclipse ECJ] Created analysis result for 0 issues (found 0 new issues, fixed 0 issues)
Finished: SUCCESS
{noformat}
Parser - indeed has *ANT*_ECLIPSE_WARNING_PATTERN in [EclipseParser.java|https://github.com/jenkinsci/analysis-model/blob/0c53a83b491b1dc32e57ff73a3f5751175448c7c/src/main/java/edu/hm/hafner/analysis/parser/EclipseParser.java#L26], not MAVEN in name, yet [Documentation|https://github.com/jenkinsci/warnings-ng-plugin/blob/master/doc/Documentation.md] promises Maven Project to be supported type.

Inspection of job's log with {{less}} shows colorised entries with control sequences like below:
{noformat}
ESC[8mha:////4ABzfsCHJFyEqbHt1tyu83RhpB1NXTka2OpStZBOt27/AACAYx+LCAAcAWZAAP9ba5aBtbi1QSWjNKU4P0+vJLE4u1gvPjexLDVPzxdEhicW5WXmpfvWl6S2eNly5fzGzaurGBgqihikoFqS8/OK83NS9ZwhlkghAwQwghQWAA14xA+XYgAbAA==ESC[0m[WARNING] /home/jenkins-agent/agent-1/workspace/xxx/.../Y.java:[167,6363] Unqualified access to the field Y.w
{noformat}
but I don't know if they are also transferred to {{ReportScanningTool}}.
----
If project is executed with modified plexus-compiler (as the currently released one does not support specifying log file [plexus-compiler#55|https://github.com/codehaus-plexus/plexus-compiler/issues/55]) - with log files preserved and fed to warnings-ng - the same build results in
{noformat}
...
channel stopped
[Eclipse ECJ] Searching for all files in '/home/jenkins-agent/agent-2/workspace/xxx' that match the pattern '**/target/ecjerr-*.xml'
[Eclipse ECJ] -> found 10 files
[Eclipse ECJ] Successfully parsed file /home/jenkins-agent/agent-2/workspace/xxx/target/ecjerr-1737547503980039210.xml
[Eclipse ECJ] -> found 7 issues (skipped 0 duplicates)
...
[Eclipse ECJ] Post processing issues on 'phobos-agent-2' with encoding 'UTF-8'
[Eclipse ECJ] Resolving absolute file names for all issues
[Eclipse ECJ] -> 0 resolved, 0 unresolved, 55 already resolved
[Eclipse ECJ] Copying affected files to Jenkins' build folder /home/yyy/.jenkins/jobs/xxx/builds/11
[Eclipse ECJ] -> 55 copied, 0 not in workspace, 0 not-found, 0 with I/O error
[Eclipse ECJ] Resolving module names from module definitions (build.xml, pom.xml, or Manifest.mf files)
[Eclipse ECJ] -> resolved module names for 381 issues
[Eclipse ECJ] Resolving package names (or namespaces) by parsing the affected files
[Eclipse ECJ] -> resolved package names of 55 affected files
[Eclipse ECJ] No filter has been set, publishing all 381 issues
[Eclipse ECJ] Creating fingerprints for all affected code blocks to track issues over different builds
[Eclipse ECJ] -> created fingerprints for 381 issues
[Eclipse ECJ] Invoking Git blamer to create author and commit information for all affected files
[Eclipse ECJ] GIT_COMMIT env = 'c23f454408747cd7c6158a69c2457c9c98154254'
[Eclipse ECJ] Git working tree = '/home/jenkins-agent/agent-2/workspace/xxx'
[Eclipse ECJ] Git commit ID = 'c23f454408747cd7c6158a69c2457c9c98154254'
[Eclipse ECJ] Job workspace = '/home/jenkins-agent/agent-2/workspace/xxx'
[Eclipse ECJ] Created blame requests for 55 files - invoking Git blame on agent for each of the requests
[Eclipse ECJ] -> blamed authors of issues in 55 files
[Eclipse ECJ] Attaching ResultAction with ID 'eclipse' to run 'xxx #11'.
[Eclipse ECJ] Using reference build 'xxx #10' to compute new, fixed, and outstanding issues
[Eclipse ECJ] Issues delta (vs. reference build): outstanding: 0, new: 381, fixed: 0
[Eclipse ECJ] No quality gates have been set - skipping
[Eclipse ECJ] Health report is disabled - skipping
[Eclipse ECJ] Created analysis result for 381 issues (found 381 new issues, fixed 0 issues)
Finished: SUCCESS
{noformat}
which proves that {{EclipseXMLParser}} is really fine.

New: Maven build using Error Prone compiler completes with:
{noformat}
channel stopped
[Error Prone] Sleeping for 5 seconds due to ~~JENKINS-32191~~...
[Error Prone] Parsing console log (workspace: '/opt/buildsystem/data/jenkins2/workspace/xxx')
[Error Prone] Attaching ResultAction with ID 'error-prone' to run 'xxx #1411'.
[Error Prone] Using reference build 'xxx #1410' to compute new, fixed, and outstanding issues
[Error Prone] Issues delta (vs. reference build): outstanding: 0, new: 0, fixed: 0
[Error Prone] Evaluating quality gates
[Error Prone] -> All quality gates have been passed
[Error Prone] Health report is disabled - skipping
[Error Prone] Created analysis result for 0 issues (found 0 new issues, fixed 0 issues)
Finished: SUCCESS
{noformat}
Inspection of job's log shows entries like the example below:
{noformat}
[pool-1-thread-3 for channel id=36910] WARNING org.apache.maven.plugin.compiler.CompilerMojo - /opt/buildsystem/data/jenkins2/workspace/xxx/xxx-module/src/main/java/a/path/SomeClass.java:[209,74] [DefaultCharset] Implicit use of the platform default charset, which can result in differing behaviour between JVM executions or incorrect behavior if the encoding of the data source doesn't match expectations.
(see https://errorprone.info/bugpattern/DefaultCharset)
Did you mean '+ Base64.encodeBase64String(aString.getBytes(UTF_8)) + "')");' or '+ Base64.encodeBase64String(aString.getBytes(Charset.defaultCharset())) + "')");'?
{noformat}

It seems the warnings are not detected (due to the 'pool-1-thread' or 'org.apache.maven.plugin.compiler.CompilerMojo' stuff?) from console log

Marco Rothe made changes - 2019-01-03 13:01

Description

Original: Maven build using Error Prone compiler completes with:
{noformat}
channel stopped
[Error Prone] Sleeping for 5 seconds due to ~~JENKINS-32191~~...
[Error Prone] Parsing console log (workspace: '/opt/buildsystem/data/jenkins2/workspace/xxx')
[Error Prone] Attaching ResultAction with ID 'error-prone' to run 'xxx #1411'.
[Error Prone] Using reference build 'xxx #1410' to compute new, fixed, and outstanding issues
[Error Prone] Issues delta (vs. reference build): outstanding: 0, new: 0, fixed: 0
[Error Prone] Evaluating quality gates
[Error Prone] -> All quality gates have been passed
[Error Prone] Health report is disabled - skipping
[Error Prone] Created analysis result for 0 issues (found 0 new issues, fixed 0 issues)
Finished: SUCCESS
{noformat}
Inspection of job's log shows entries like the example below:
{noformat}
[pool-1-thread-3 for channel id=36910] WARNING org.apache.maven.plugin.compiler.CompilerMojo - /opt/buildsystem/data/jenkins2/workspace/xxx/xxx-module/src/main/java/a/path/SomeClass.java:[209,74] [DefaultCharset] Implicit use of the platform default charset, which can result in differing behaviour between JVM executions or incorrect behavior if the encoding of the data source doesn't match expectations.
(see https://errorprone.info/bugpattern/DefaultCharset)
Did you mean '+ Base64.encodeBase64String(aString.getBytes(UTF_8)) + "')");' or '+ Base64.encodeBase64String(aString.getBytes(Charset.defaultCharset())) + "')");'?
{noformat}

It seems the warnings are not detected (due to the 'pool-1-thread' or 'org.apache.maven.plugin.compiler.CompilerMojo' stuff?) from console log

New: Maven build using Error Prone compiler completes with:
{noformat}
channel stopped
[Error Prone] Sleeping for 5 seconds due to ~~JENKINS-32191~~...
[Error Prone] Parsing console log (workspace: '/opt/buildsystem/data/jenkins2/workspace/xxx')
[Error Prone] Attaching ResultAction with ID 'error-prone' to run 'xxx #1411'.
[Error Prone] Using reference build 'xxx #1410' to compute new, fixed, and outstanding issues
[Error Prone] Issues delta (vs. reference build): outstanding: 0, new: 0, fixed: 0
[Error Prone] Evaluating quality gates
[Error Prone] -> All quality gates have been passed
[Error Prone] Health report is disabled - skipping
[Error Prone] Created analysis result for 0 issues (found 0 new issues, fixed 0 issues)
Finished: SUCCESS
{noformat}
Inspection of job's log shows entries like the example below:
{noformat}
[pool-1-thread-3 for channel id=36910] WARNING org.apache.maven.plugin.compiler.CompilerMojo - /pathtoworkspace/workspace/xxx/xxx-module/src/main/java/a/path/SomeClass.java:[209,74] [DefaultCharset] Implicit use of the platform default charset, which can result in differing behaviour between JVM executions or incorrect behavior if the encoding of the data source doesn't match expectations.
    (see https://errorprone.info/bugpattern/DefaultCharset)
  Did you mean '+ Base64.encodeBase64String(aString.getBytes(UTF_8)) + "')");' or '+ Base64.encodeBase64String(aString.getBytes(Charset.defaultCharset())) + "')");'?
{noformat}
It seems that the warnings are not detected (due to the 'pool-1-thread' or 'org.apache.maven.plugin.compiler.CompilerMojo' stuff?) from console log.

A local build (using the same maven, java and error-prone version) show the warning in the form below:
{noformat}
[WARNING] <pathtoworkspace>/SomeClass.java:[209,74] [DefaultCharset] Implicit use of the platform default charset, which can result in differing behaviour between JVM executions or incorrect behavior if the encoding of the data source doesn't match expectations.
    (see https://errorprone.info/bugpattern/DefaultCharset)
  Did you mean '+ Base64.encodeBase64String(aString.getBytes(UTF_8)) + "')");' or '+ Base64.encodeBase64String(aString.getBytes(Charset.defaultCharset())) + "')");'?
{noformat}
So there is obviously a difference in console-log formating.

Marco Rothe made changes - 2019-01-03 13:01

Description

Original: Maven build using Error Prone compiler completes with:
{noformat}
channel stopped
[Error Prone] Sleeping for 5 seconds due to ~~JENKINS-32191~~...
[Error Prone] Parsing console log (workspace: '/opt/buildsystem/data/jenkins2/workspace/xxx')
[Error Prone] Attaching ResultAction with ID 'error-prone' to run 'xxx #1411'.
[Error Prone] Using reference build 'xxx #1410' to compute new, fixed, and outstanding issues
[Error Prone] Issues delta (vs. reference build): outstanding: 0, new: 0, fixed: 0
[Error Prone] Evaluating quality gates
[Error Prone] -> All quality gates have been passed
[Error Prone] Health report is disabled - skipping
[Error Prone] Created analysis result for 0 issues (found 0 new issues, fixed 0 issues)
Finished: SUCCESS
{noformat}
Inspection of job's log shows entries like the example below:
{noformat}
[pool-1-thread-3 for channel id=36910] WARNING org.apache.maven.plugin.compiler.CompilerMojo - /pathtoworkspace/workspace/xxx/xxx-module/src/main/java/a/path/SomeClass.java:[209,74] [DefaultCharset] Implicit use of the platform default charset, which can result in differing behaviour between JVM executions or incorrect behavior if the encoding of the data source doesn't match expectations.
    (see https://errorprone.info/bugpattern/DefaultCharset)
  Did you mean '+ Base64.encodeBase64String(aString.getBytes(UTF_8)) + "')");' or '+ Base64.encodeBase64String(aString.getBytes(Charset.defaultCharset())) + "')");'?
{noformat}
It seems that the warnings are not detected (due to the 'pool-1-thread' or 'org.apache.maven.plugin.compiler.CompilerMojo' stuff?) from console log.

A local build (using the same maven, java and error-prone version) show the warning in the form below:
{noformat}
[WARNING] <pathtoworkspace>/SomeClass.java:[209,74] [DefaultCharset] Implicit use of the platform default charset, which can result in differing behaviour between JVM executions or incorrect behavior if the encoding of the data source doesn't match expectations.
    (see https://errorprone.info/bugpattern/DefaultCharset)
  Did you mean '+ Base64.encodeBase64String(aString.getBytes(UTF_8)) + "')");' or '+ Base64.encodeBase64String(aString.getBytes(Charset.defaultCharset())) + "')");'?
{noformat}
So there is obviously a difference in console-log formating.

New: Maven build using Error Prone compiler completes with:
{noformat}
channel stopped
[Error Prone] Sleeping for 5 seconds due to ~~JENKINS-32191~~...
[Error Prone] Parsing console log (workspace: '/pathtoworkspace/workspace/xxx')
[Error Prone] Attaching ResultAction with ID 'error-prone' to run 'xxx #1411'.
[Error Prone] Using reference build 'xxx #1410' to compute new, fixed, and outstanding issues
[Error Prone] Issues delta (vs. reference build): outstanding: 0, new: 0, fixed: 0
[Error Prone] Evaluating quality gates
[Error Prone] -> All quality gates have been passed
[Error Prone] Health report is disabled - skipping
[Error Prone] Created analysis result for 0 issues (found 0 new issues, fixed 0 issues)
Finished: SUCCESS
{noformat}
Inspection of job's log shows entries like the example below:
{noformat}
[pool-1-thread-3 for channel id=36910] WARNING org.apache.maven.plugin.compiler.CompilerMojo - /pathtoworkspace/workspace/xxx/xxx-module/src/main/java/a/path/SomeClass.java:[209,74] [DefaultCharset] Implicit use of the platform default charset, which can result in differing behaviour between JVM executions or incorrect behavior if the encoding of the data source doesn't match expectations.
    (see https://errorprone.info/bugpattern/DefaultCharset)
  Did you mean '+ Base64.encodeBase64String(aString.getBytes(UTF_8)) + "')");' or '+ Base64.encodeBase64String(aString.getBytes(Charset.defaultCharset())) + "')");'?
{noformat}
It seems that the warnings are not detected (due to the 'pool-1-thread' or 'org.apache.maven.plugin.compiler.CompilerMojo' stuff?) from console log.

A local build (using the same maven, java and error-prone version) show the warning in the form below:
{noformat}
[WARNING] <pathtoworkspace>/SomeClass.java:[209,74] [DefaultCharset] Implicit use of the platform default charset, which can result in differing behaviour between JVM executions or incorrect behavior if the encoding of the data source doesn't match expectations.
    (see https://errorprone.info/bugpattern/DefaultCharset)
  Did you mean '+ Base64.encodeBase64String(aString.getBytes(UTF_8)) + "')");' or '+ Base64.encodeBase64String(aString.getBytes(Charset.defaultCharset())) + "')");'?
{noformat}
So there is obviously a difference in console-log formating.

Ulli Hafner made changes - 2019-01-15 11:25

Rank

New: Ranked higher

Ulli Hafner made changes - 2019-01-15 11:29

Rank

New: Ranked higher

Ulli Hafner made changes - 2019-01-15 11:40

Rank

New: Ranked higher

Ulli Hafner made changes - 2019-02-13 11:57

Resolution		New: Cannot Reproduce [ 5 ]
Status	Original: Open [ 1 ]	New: Resolved [ 5 ]

Marco Rothe made changes - 2024-04-05 17:07

Link

New: This issue is related to ~~JENKINS-72976~~ [ ~~JENKINS-72976~~ ]

Assignee:: Ulli Hafner

Reporter:: Marco Rothe

Votes:: 0 Vote for this issue

Watchers:: 3 Start watching this issue

Created:: 2019-01-03 12:45

Updated:: 2024-04-05 17:07

Resolved:: 2019-02-13 11:57

Details

Description

Attachments

Issue Links

Activity

People

Dates