MaxCallChainLength: Value of 1 results in more issues that a value of 2

Issue #52 resolved

Tobias Becker created an issue 2015-03-02

I could only find one instance of this happening with ireport Output (and -eclipse output for easy diff) attached

Comments (8)

Tobias Becker reporter
- attached bin.zip
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
- 2015-03-02T17:28:57+00:00
Michael Eichberg 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.)
- 2015-03-02T18:41:58+00:00
Michael Eichberg repo owner
- marked as minor
- marked as enhancement
- 2015-03-02T18:42:32+00:00
Tobias Becker reporter
Still 36 issues with maxCallChainLength=2 and -maxEvalFactor=99.0
- 2015-03-02T19:00:44+00:00
Tobias Becker reporter
Re-run it with -maxEvalFactor=Infinity, still 36 issues.
- 2015-03-04T19:30:14+00:00
Michael Eichberg repo owner
- changed status to resolved
fixed issue ~~#52~~

→ <<cset c2d6104d3e0f>>
- 2015-03-06T17:34:59+00:00
Michael Eichberg repo owner
- removed milestone
Removing milestone: 0.8.0-M3 (automated comment)
- 2016-04-26T15:19:26+00:00
Michael Eichberg repo owner
- removed version
Removing version: 0.8.0 (automated comment)
- 2017-04-27T22:32:37+00:00
Log in to comment