|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Master:
java version "1.7.0_55"
OpenJDK Runtime Environment (rhel-2.4.7.1.el6_5-x86_64 u55-b13)
OpenJDK 64-Bit Server VM (build 24.51-b03, mixed mode)
Example slave:
java version "1.6.0_41"
Java(TM) SE Runtime Environment (build 1.6.0_41-b02)
Java HotSpot(TM) 64-Bit Server VM (build 20.14-b01, mixed mode)
Cppcheck 1.57
Other slave with same problem (on different jobs):
java version "1.6.0_65"
Java(TM) SE Runtime Environment (build 1.6.0_65-b14-462-11M4609)
Java HotSpot(TM) 64-Bit Server VM (build 20.65-b04-462, mixed mode)
Cppcheck 1.61
Cppcheck command:
cppcheck -i$PATH1 -i$PATH2 -i$PATH3 --xml --enable=style -j 2 $PATH4 2> cppcheck-int.xml
xsltproc cppcheck.xslt cppcheck-int.xml > cppcheck-result.xml
The XSLT is changing some "style" issues to "warning" and "performance". According to comments, this is because the --xml option changed everything that wasn't an "error" into "style". I can't see a logical reason why this would affect your plugin.
I'll try upgrading cppcheck and look at the options you recommend. This may prove the XSLT to be unnecessary and fix the count issue as well.
If that doesn't help, I'll try the test jobs you asked for.