The concern here is that a failure in the code under test shouldn't cause an internal error in Gradle. If you don't mind, please post the stack trace anyway so that someone can look into why Gradle didn't more gracefully handle the failure.
On Mon, Aug 9, 2010 at 2:08 PM, Ben Jansen <[email protected]> wrote: > Adam Murdoch <a...@...> writes: > > > test { > > afterSuite { suite, result -> > > result.exception?.printStackTrace() > > } > > } > > > > (or you could run your build with trunk to see the stack trace) > > > > Could you run this and send in the stack trace? > > Thanks for your reply! The afterSuite block revealed the failure was an > exception in my test code. I'll leave the block in until a release which > includes the missing stack trace fix. > > Thanks again, > Ben > > -- John Murph Automated Logic Research Team
