i noticed that because i regularily build and install the SNAPSHOT on my windows system (xp sp2).
i did a -Dskip.test and -Dskip.integTest to overcome this. i did not mention it in the forums as i am too new in gradle. may be next time i will have the guts to do so ;-) IMO the ci-build is exectly the right tool to avoid that situation ... have a nice day. hdockter wrote: > > Hi, > > we had a regression bug that Gradle always returns exit value 0, even > in case of an error. Since September 9 there are unit tests failing > specifically under Windows (none of the Gradle developers is using > this OS). Our windows CI build did not signal this failing unit tests > because of the above bug. Fortunately those were bugs just in the > unit tests and not in our production code. > > The real problem is not the bug, but the fact that none of our tests > did detect this. I'm going to add a couple of integration tests to > check process return value behaviour. > > Adam, I guess we have to draw lots for who of us must switch to > windows ;) > > - Hans > > -- > Hans Dockter > Gradle Project lead > http://www.gradle.org > > > > > > --------------------------------------------------------------------- > To unsubscribe from this list, please visit: > > http://xircles.codehaus.org/manage_email > > > > -- View this message in context: http://www.nabble.com/Failing-Test-under-Windows-in-Stealth-Mode-tp19549289p19550262.html Sent from the gradle-dev mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
