-
Notifications
You must be signed in to change notification settings - Fork 135
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Can not execute Findbugs with a timeout threshold value of 600000 milliseconds #254
Comments
This issue persist in following combination also. |
I think the issue can be resolved, refer #50 |
As per #50 , it works fine with |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I am facing the issue: Can not execute Findbugs with a timeout threshold value of 600000 milliseconds
This issue encountered after added Findbugs plugin into sonarqube.
sonarqube-6.7.6
Findbugs 3.9.2
Java 1.8
With 600000 Timeout:
INFO: 0/0 source files have been analyzed
INFO: Sensor JavaSquidSensor [java] (done) | time=7560ms
INFO: Sensor FindBugs Sensor [findbugs]
INFO: Loading findbugs plugin: /Cisco/dcnm_repo/dcnm_new/nms/com/cisco/dcbu/vinci/utils/.scannerwork/findbugs/findsecbugs-plugin.jar
INFO: Findbugs output report: /Cisco/dcnm_repo/dcnm_new/nms/com/cisco/dcbu/vinci/utils/.scannerwork/findbugs-result.xml
INFO: ------------------------------------------------------------------------
INFO: EXECUTION FAILURE
INFO: ------------------------------------------------------------------------
INFO: Total time: 10:24.412s
INFO: Final Memory: 2880M/3730M
INFO: ------------------------------------------------------------------------
ERROR: Error during SonarQube Scanner execution
ERROR: Can not execute Findbugs with a timeout threshold value of 600000 milliseconds
ERROR:
ERROR: Re-run SonarQube Scanner using the -X switch to enable full debug logging.
With 7200000 Timeout:
01:27:46.920 INFO: Findbugs output report: /Cisco/dcnm_repo/dcnm_new/nms/com/cisco/dcbu/vinci/utils/.scannerwork/findbugs-result.xml
02:13:27.194 WARN: [JOURNAL_FLUSHER] WARNING Journal flush operation took 17,253ms last 8 cycles average is 2,156ms
02:20:46.420 WARN: [JOURNAL_FLUSHER] WARNING Journal flush operation took 7,385ms last 8 cycles average is 3,079ms
02:25:49.816 WARN: [JOURNAL_FLUSHER] WARNING Journal flush operation took 37,048ms last 8 cycles average is 7,711ms
02:32:20.710 WARN: [JOURNAL_FLUSHER] WARNING Journal flush operation took 26,867ms last 8 cycles average is 11,069ms
Is there any Fix / Workaround available?
The text was updated successfully, but these errors were encountered: