[ 
https://issues.jenkins-ci.org/browse/JENKINS-10949?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161714#comment-161714
 ] 

Jan Klass commented on JENKINS-10949:
-------------------------------------

So this is not an issue of the plugin and should thus be placed in the cppcheck 
issue tracker.

About your problem with ""c:/ci-scripts/util/cppcheckgui.exe" -j 15 
--enable=all --force --verbose --xml --xml-version=2 . > cppcheck.xml":
You forgot to "2 > cppcheck.xml" (missing 2); this redirects stderr to the xml 
file. The xml is passed to xml.

The first thing I’d try is not use --verbose. Often the verbose flag is used 
for more output while executing. Although the description for cppcheck implies 
its only on the error reports, additional scans may apply. Try removing it.
Also, if you don't need progress information, try -q for quiet. I/O always 
takes up time.

On your GUI-try you used -j, on the jenkins execution you did not. So the 
difference here is probably what you want to look into (seems you already do).
                
> Jenkins CPPCheck is running too slow
> ------------------------------------
>
>                 Key: JENKINS-10949
>                 URL: https://issues.jenkins-ci.org/browse/JENKINS-10949
>             Project: Jenkins
>          Issue Type: Bug
>          Components: cppcheck
>    Affects Versions: current
>         Environment: Jenkins is running on a Windows 2008 R2 server slave 
> machine with 16 processors.
> The version of Jenkins CPPCheck I'm currently using is 1.0.0
>            Reporter: Surya NV
>            Assignee: gbois
>
> CPPcheck is running way too slow(both via Jenkins job and when run from 
> command line directly) and hasn't completed after 8 days now. There are 2500 
> files in total and it has just gotten to 30% of the files after 8 days now. 
> Here is the command I'm using: 
> "c:/ci-scripts/util/cppcheck" --enable=all --force --verbose --xml 
> --xml-version=2 . 2> cppcheck.xml
> The other jobs that run similar cppchecks for a fewer number of files such as 
> 150 seem to complete in 30-40 minutes. I was assuming that 2500 files would 
> complete in roughly 5-6 hours.
> Are there any options to expedite the cppcheck process? Please let me know.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


Reply via email to