For archive-reading junkies...that issue has been addressed and the bad news is no longer news :)
-Tom On Mon, Jan 28, 2013 at 9:57 PM, Hirotsugu Asari <asari.r...@gmail.com> wrote: > > On Jan 27, 2013, at 10:16 AM, Hirotsugu Asari <asari.r...@gmail.com> wrote: > > As you have probably noticed, Travis has been having issues with their JVM > workers. The symptom is such that JVM jobs die unexpectedly with OOM errors. > I am working with Travis team and Blue Box (their VM provider) to get this > resolved as soon as we can. > > In the meantime, our best bet is vigorous local testing. I apologize for the > inconvenience, and appreciate your patience. > > > I have good news and bad news. > > The good news is that the JVM issue seems to have been addressed. I re-ran > some previously failing builds, and some passed. > (https://travis-ci.org/jruby/jruby/builds/4364264, > https://travis-ci.org/jruby/jruby/builds/4403460). > > The bad news is that master branch is broken. > https://travis-ci.org/jruby/jruby/builds/4443066 I opened a ticket on > github. https://github.com/jruby/jruby/issues/516 -- blog: http://blog.enebo.com twitter: tom_enebo mail: tom.en...@gmail.com --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
