On 06/01/2013, at 20:04, Adam Murdoch <[email protected]> wrote:
> > On 06/01/2013, at 9:55 PM, Luke Daley wrote: > >> This is happening consistently. >> >> Anyone have any idea why? (before I start investigating tomorrow) > > It's the JNA crash we've been seeing for a while now. It'll go away once we > stop using JNA (after we branch for 1.4). If you want to do something about > it before then, you could change the in-process int tests on windows to use a > low forkEvery setting, or change the windows commit build to use forking int > tests. I won't do this, given that it's a known problem and we have a next step outlined. > >> >> Begin forwarded message: >> >>> From: [email protected] >>> Date: 6 January 2013 10:31:09 GMT >>> To: [email protected] >>> Subject: [TeamCity, FAILED] Build Gradle - Master - Commit Builds :: >>> Windows - Java 1.6 #499 >>> >>> Build Gradle - Master - Commit Builds :: Windows - Java 1.6 #499 failed >>> (JVM crashed; tests passed: 7808, ignored: 101; process exited with code 1) >>> Agent: winagent perf1 >>> >>> >>> Changes included: 2 changes. >>> Change 8824732a03d9d8db1ab30fc07eb745de9982baae by adam.murdoch (4 files): >>> Moved handling of indentation in SimpleXmlWriter, and use platform line >>> separator in generated xml. >>> Change c20cd41a96bd53e4b054c370dde2b05dcf70d2c5 by adam.murdoch (2 files): >>> Switched back to 1.3 again. >>> >>> >>> Configure your email notifications on your settings page. > > > -- > Adam Murdoch > Gradle Co-founder > http://www.gradle.org > VP of Engineering, Gradleware Inc. - Gradle Training, Support, Consulting > http://www.gradleware.com >
