That is good news :) It would still be nice to figure out what the actual failure was to make sure this was building properly for any version the user might have, do you guys think you can configure the maven jobs to run with -e whenever future issues like this occur? That would also be nice ;)
Anyway, good work guys! On Wed, May 27, 2015 at 7:05 PM, Daan Hoogland <daan.hoogl...@gmail.com> wrote: > put it to 1.8 latest and maven 3 latest. this should work as well. > > Op wo 27 mei 2015 om 19:04 schreef Daan Hoogland <daan.hoogl...@gmail.com > >: > > > I noticed, i configured 1.8 (hope you beat me to it so mine won) will > > check what's in there now. > > > > Op wo 27 mei 2015 om 18:03 schreef David Nalley <da...@gnsa.us>: > > > > Yesterday Andrew Bayer located the problem: > >> > >> May-26 3:09 PM > >> Found it - it does not like java 1.7.0_65 for some reason. > >> [May-26 3:10 PM] Andrew Bayer: Works fine with 1.7.0_72, which is what > >> the "latest1.7" JDK option on builds.a.o gets you (not the Java 1.7 > >> (latest) one, that gets you 65, because confusion). Rerunning now... > >> > >> And since then it appears to be working properly. > >> > >> --David > >> > >> On Fri, May 22, 2015 at 7:52 PM, David Nalley <da...@gnsa.us> wrote: > >> > You are almost certainly not going to get access to the slaves. > >> > I'll see if the Infra Jenkins guy can peer into what's going on and > >> > why - though I think Rafael's later response is perhaps pragmatic. > >> > > >> > --David > >> > > >> > On Fri, May 22, 2015 at 1:43 PM, Daan Hoogland < > daan.hoogl...@gmail.com> > >> wrote: > >> >> I've been asking infra about this. i have no idea how to access those > >> >> slaves. see https://issues.apache.org/jira/browse/BUILDS-81 > >> >> > >> >> Op vr 22 mei 2015 om 19:37 schreef Rafael Fonseca < > >> rsafons...@gmail.com>: > >> >> > >> >>> Hi guys, > >> >>> > >> >>> This Jenkins build failure in OVM3 is starting to annoy me.. can > >> anyone > >> >>> help/grant access to the apache build site/slaves, either to add > some > >> >>> config to the Jenkins job to produce useful output on failures or to > >> track > >> >>> the issue on the failing slaves themselves? > >> >>> > >> >>> This is failing only on specific build hosts... > >> >>> > >> >>> Rafael > >> >>> > >> > > >
