search

pear / jenkins-configuration

2 stars 2 forks source link

Clover causes build to fail when all tests are skipped #8

Open convissor opened 12 years ago

convissor commented 12 years ago

When all tests in a package are skipped, no code coverage is generated. So when clover goes to build a report, it complains there is no information for it, so fails the project build. It seems like the outcome should rather be something neutral (neither pass nor fail).

See test.pear.php.net:8080/job/Services_Atlassian_Crowd/11/console for an example. Here's what it outputs:

Publishing Clover coverage report...
Clover xml file does not exist in: /var/lib/jenkins/workspace/Services_Atlassian_Crowd called: build/logs/clover.xml and will not be copied to: /var/lib/jenkins/jobs/Services_Atlassian_Crowd/builds/2012-01-06_10-41-30/cloverphp/clover.xml
Could not find 'build/coverage/build/logs/clover.xml'.  Did you generate the XML report for Clover?
Recording test results
None of the test reports contained any result
Build step 'Publish JUnit test result report' changed build result to FAILURE
Finished: FAILURE
CloCkWeRX commented 12 years ago

This is actually just junit failing: "None of the test reports contained any result". If you remove the clover bits... it'll still fail. It's a phpunit/junit output problem tbh.