Thanks Daz for reminder :) I know about this issue - some of the CI builds also reported this issue. I'm in the process of reworking this task history cache and it'll get fixed soon.
Sorry for inconvenience! On Sun, Sep 8, 2013 at 8:02 PM, Daz DeBoer <darrell.deb...@gradleware.com>wrote: > G'day > I've just updated and installed from latest master and am using it to run > some local builds. > When I use the daemon, a task failure leaves Gradle in a bad state, that > can only be recovered by 'gradle --stop'. This issue doesn't happen when I > run without the daemon. > > The failing task in my case is a CppCompile task, but I've also seen this > with a failing LinkExecutable task. I suspect the actual task isn't overly > relevant. > > Here's the stack trace of the failure: > https://gist.github.com/bigdaz/4bd4039284f868a11776 > > @Szczepan I suspect this is involved in the stuff you're doing. Not a big > issue for me, but I wanted to report. > > Daz > > -- Szczepan Faber core dev@gradle; lead@mockito Join me at the Gradle eXchange 2013, Oct 28th in London: http://skillsmatter.com/event/java-jee/gradle-exchange-2013
