Hi,
Building an m2 single-module project on Jenkins 1.485 and we are seeing two 
(possibly related) problems.

Firstly, occasionally we are seeing the build have it's module marked as 
(didn't run) when from the console it is clear that it did.

Secondly, we are seeing test failures and the build is still marked as 
successful not unstable. What is odd about this, is that jenkins still 
"knows" that the job is unstable because it doesn't trigger downstream 
projects.

Anyone else seeing this or know what the problem might be?



 

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.


Reply via email to