That would be because hudson turns off failing a build if tests fail. In hudson, failing tests is a yellow ball.
Build broken is a red ball Everything hunky-dory is a blue ball. your issue comes from using the crappy maven 2 project type in hudson which modifies your build behind your back. Use freestyle and ensure that the test reports pattern matches all your output directories and you'll get your yellow balls again (assuming you add -Dmaven.test.failure.ignore=true so that your hudson build can give yellow balls) By the way, yellow balls are better because they tell you how many tests are failing... Developer builds should fail fast. CI builds should report how badly the tests are failing to allow you to track progress - Stephen --- Sent from my Android phone, so random spelling mistakes are a direct result of using swype to type on the screen On 10 Nov 2010 18:01, "Bogdan Calmac" <[email protected]> wrote: OK, I've done some further investigation and discovered that this only happens on our Hudson CI server. The cmdline maven build works as expected. For reference, here is the JIRA for the Hudson project: http://issues.hudson-ci.org/browse/HUDSON-8065 -- View this message in context: http://maven.40175.n5.nabble.com/Running-tests-twice-and-the-build-success-status-tp3257693p3259119.html Sent from the Maven - Users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: users-...
