On Fri, Nov 18, 2011 at 22:15, Luke Daley <luke.da...@gradle.biz> wrote:
> On 18/11/2011, at 8:25 PM, Guillaume Laforge <glafo...@gmail.com> wrote: > > I'm still wondering if that could be something in my codebase also that > could be influencing that strange behaviour. > My code base has evolved since when it was failing a few days ago, and > I've tried running again the build with gradle test, and then it wasn't > hanging anymore. > Perhaps going back through an older revision I could find a point where it > was failing. > In my tests, I'm using the unit testing classes of the Google App Engine > SDK, which use thread locals and probably other tricks... perhaps it could > be launching some daemon threads or something (but I'd expect to see them > though in the traces). > Could you think of something that a test could be doing, that could > prevent Gradle from doing its job? > And interesting... something that would not prevent IntelliJ from > exhibiting the same behaviour... > > > Running from IntelliJ bypasses all of our messaging infrastructure, which > is almost certainly where the problem is so there is no surprise there. > > I don't think your code is involved directly as, like you said, you'd > expect to see it in the stacks if it were. There ate no tests running in > these stacks. > > We can reproduce this outside of your project with m4 onwards, so it's not > a direct link but something about gaelyk is triggering this a lot. > > I'm starting to suspect it's something stdio related for a few reasons but > it's too early to tell. Hopefully we'll know more soon. > Okie dokie. If ever I can do something to help further debug the problem, don't hesitate. -- Guillaume Laforge Groovy Project Manager SpringSource, a division of VMware Blog: http://glaforge.appspot.com/ Twitter: @glaforge <http://twitter.com/glaforge> Google+: http://gplus.to/glaforge
