AbstractBugReporter emits wrong non-sensical debug output during filtering #184
Labels
Comments
Alex-Vol-Amz
added a commit
to Alex-Vol-Amz/spotbugs
that referenced
this issue
Jan 2, 2023
The logic conditionals were entangled in an invalid way that produced nonsense debug log messages. Simplified the logic and reduced the logic branches to make the operation direct and thus fix the problem.
Alex-Vol-Amz
added a commit
to Alex-Vol-Amz/spotbugs
that referenced
this issue
Jan 2, 2023
The logic conditionals were entangled in an invalid way that produced nonsense debug log messages. Simplified the logic and reduced the logic branches to make the operation direct and thus fix the problem.
hazendaz
pushed a commit
that referenced
this issue
Jan 5, 2023
* Fix Issue #184 The logic conditionals were entangled in an invalid way that produced nonsense debug log messages. Simplified the logic and reduced the logic branches to make the operation direct and thus fix the problem. * Added unit test to prove correct behavior of priority and rank This unit test serves as proof that the reportBug function is operating as expected with respect to reporting based on priority and rank threshold values. As a bonus this test also verifies that the relaxed mode will override any rank or priority and always report bugs found.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Either the filtering logic or the debug output in
AbstractBugReporteris wrong. With-Dabreporter.debug=trueset, I just got the following non-sensical output:Neither inequality is true.
The text was updated successfully, but these errors were encountered: