- attached bin.zip
MaxCallChainLength: Value of 1 results in more issues that a value of 2
Issue #52
resolved
I could only find one instance of this happening with ireport Output (and -eclipse output for easy diff) attached
Comments (8)
-
reporter -
repo owner can you please repeat the test for maxCallChainLength=2 with -maxEvalFactor=99.0 (If method in report are particularly long it may happen that some analyses (using level 2) are completely aborted to come to an end and, hence, some issues are not reported at all.)
-
repo owner - marked as minor
- marked as enhancement
-
reporter Still 36 issues with maxCallChainLength=2 and -maxEvalFactor=99.0
-
reporter Re-run it with -maxEvalFactor=Infinity, still 36 issues.
-
repo owner - changed status to resolved
fixed issue
#52→ <<cset c2d6104d3e0f>>
-
repo owner - removed milestone
Removing milestone: 0.8.0-M3 (automated comment)
-
repo owner - removed version
Removing version: 0.8.0 (automated comment)
- Log in to comment
runMain org.opalj.bugpicker.core.Console -cp=D:\Studium\OPAL\QC\Systems\ireport\ireport-3.7.5\bin -libcp="C:\Program Files\Java\jre1.8.0_20\lib" -kinds="dead path" -minRelevance=5 -maxEvalFactor=15.0 -maxEvalTime=15000 -eclipse -maxCallChainLength=2