You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
groovy diff.groovy --localGitRepo [location of checkstyle project] --baseBranch [branch name without fix] --patchBranch [branch name with fix] --config magic-number-config.xml --listOfProjects test.properties -xm -Dcheckstyle.failsOnError=false --allowExcludes
Some analysis
After investigation, this difference presents before the results are sent to patch-diff-report-tool to compare. This difference is presented in checkstyle-result.xml. For example:
<filename="/Users/liminghao/Programs/IdeaProjects/contribution/checkstyle-tester/repositories/elasticsearch/src/test/java/org/elasticsearch/script/ScriptFieldTests.java">
<errorline="1"severity="error"message="Got an exception - java.lang.NullPointerException "source="com.puppycrawl.tools.checkstyle.Checker"/>
</file>
This means, when the checkstyle report is generated, this difference is already there. I also noticed that the single line stacktrace has 
(\n) at the very end. This might be the cause of the incorrect termination of the line.
The text was updated successfully, but these errors were encountered:
Discovered at checkstyle/checkstyle#14791 (comment)
Regression report displays exceptions inconsistently.
Sometimes there is a full stacktrace for an exception:
https://checkstyle-diff-reports.s3.us-east-2.amazonaws.com/8039a13_2024203306/reports/diff/elasticsearch/index.html#A139
Sometimes there is only a line of the exception name:
https://checkstyle-diff-reports.s3.us-east-2.amazonaws.com/8039a13_2024203306/reports/diff/elasticsearch/index.html#A1
Both these two cases came from the same report generation:
https://checkstyle-diff-reports.s3.us-east-2.amazonaws.com/8039a13_2024203306/reports/diff/index.html
To reproduce
Diff Regression config: https://gist.githubusercontent.com/Lmh-java/95ba8a3850cf6d670b2d65262531fb35/raw/7f17357bf8ec422286181c2d470ed578f8da485d/magic-number-config.xml
project lists: use the default (or only the following line for bare minimum)
groovy diff.groovy --localGitRepo [location of checkstyle project] --baseBranch [branch name without fix] --patchBranch [branch name with fix] --config magic-number-config.xml --listOfProjects test.properties -xm -Dcheckstyle.failsOnError=false --allowExcludes
Some analysis
After investigation, this difference presents before the results are sent to
patch-diff-report-tool
to compare. This difference is presented incheckstyle-result.xml
. For example:This means, when the checkstyle report is generated, this difference is already there. I also noticed that the single line stacktrace has


(\n) at the very end. This might be the cause of the incorrect termination of the line.The text was updated successfully, but these errors were encountered: