Note that there are some explanatory texts on larger screens.

plurals
  1. POphpUnderControl and PHPUnit always failing build with code 255
    primarykey
    data
    text
    <p>I have the following <code>build.xml</code> file setup in phpUnderControl.</p> <pre><code> &lt;target name="phpunit"&gt; &lt;exec executable="phpunit" dir="${basedir}/httpdocs" failonerror="on"&gt; &lt;arg line="--log-junit ${basedir}/build/logs/phpunit.xml --coverage-clover ${basedir}/build/logs/phpunit.coverage.xml --coverage-html ${basedir}/build/coverage --colors ${basedir}/httpdocs/qc/unit/CalculatorTest.php" /&gt; &lt;/exec&gt; &lt;/target&gt; </code></pre> <p>For some unkown reason the build always fails with the below message.</p> <pre><code>phpunit: [exec] PHPUnit 3.4.15 by Sebastian Bergmann. [exec] BUILD FAILED /opt/cruisecontrol-bin-2.8.3/projects/citest.local/build.xml:30: exec returned: 255 </code></pre> <p>I have run the very simple unit test manually within the unit directory and PHPUnit returns.</p> <pre><code>PHPUnit 3.4.15 by Sebastian Bergmann. . Time: 0 seconds, Memory: 5.25Mb OK (1 test, 1 assertion) </code></pre> <p>Does anyone know why it keeps failing the build, when all the tests are fine?</p> <p>My build script does have a clean method which removes and log files, so its not that. I have also manually removed the log files, just in case it's that script. And changed the owner of the log directories so they are writable.</p> <p>If it makes any difference the phpunit.xml is empty after PHPUnit is run.</p> <p>Thanks.</p> <p>UPDATE: Incidentally if I remove <code>failonerror="on"</code> it works, obviously, but PHPUnit still returns 255 and I do want it to fail on any errors, the issue is there isn't any errors yet it still fails!</p>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload