our SonarScanner had some problems on the last run; cause: “not enough space on disk”. Also some (I think consecutive) errors occurred in the logfile after running out of disk space. Especially “ERROR: ECJ: Unable to parse file; java.lang.IllegalStateException: invalid environment settings”.
But the complete job has not failed. (It analysed about a fifth of the files correctly.)This resulted in:
- 100k issues closed
- 25k issues of rule “Java parser failure” created
This means, if we fix the problem, many new issues are created.
-> In my opinion this is not the best error handling.
- Why not failing the job on “out of disk space”
- Why not failing the job on “Java parser failure”
SonarQube Scanner 126.96.36.1998
SonarQube Server 7.9.1
SonarJava 6.1 (build 20866
not enough disk space exception: potential root cause.txt (4.8 KB)
ERROR: ECJ: Unable to parse file: invalid environment settings.txt (3.5 KB)
not a valid line offset for pointer.txt (14.3 KB)
first part of whole log: firstPartOfFullLog.txt (3.8 MB)