Timeout while executing an external tool leads to a crash
While executing an external tool, if its timeout is exceeded, the analysis crashes:
Caused by: Timeout exceeded: 1800000 ms [command: php D:\JI1\workspace\Nemo-php\.sonar\phpunit-3.7.20.phar --log-junit=D:\JI1\workspace\Nemo-php\.sonar\phpunit.xml --coverage-clover=D:\JI1\workspace\Nemo-php\.sonar\phpunit.coverage.xml --configuration=phpunit.xml.dist]
For all the external tools, the default value for the timeout is 30 minutes. It can be tuned:
# Value to set in minutes sonar.phpCodesniffer.timeout=30 sonar.phpDepend.timeout=40 sonar.phpPmd.timeout=50 sonar.phpUnit.timeout=60
I have projects that do not use the required versions of PHPUnit, PHP Depend, etc. What can I do?
You also have to make sure that the output file log is compatible with the one specified by the version of the tool you want to use.
When analyzing a large PHP project, PHP hangs or ends with a unusual return code
PHP executable may have reached its maximum allocated memory. Increase the memory_limit value in your php.ini file. For example the file is located in /etc/php5/cli/php.ini on Ubuntu.
; Maximum amount of memory a script may consume (128MB) ; http://php.net/memory-limit memory_limit = 512M
When analyzing large PHP project, Maven hangs with a Java heap space message
Increase the maximum heap memory allocated for Maven by setting the environment variable MAVEN_OPTS.
When analyzing a large PHP project, PHP Depend hangs with an error code 255 and message saying "Maximum function nesting level of ‘100′ reached"