Re: Build failed in Jenkins: Log4j 2 3.x #148

> On Jul 21, 2018, at 8:24 AM, Dominik Psenner wrote: > > Jenkins slaves currently have very low disk space. This may be a out of > disk space in disguise. I definitely agree with that thought. Disk space issues cause all sorts of weird exceptions in Jenkins because that’s its data storage m

Re: Build failed in Jenkins: Log4j 2 3.x #148

Jenkins slaves currently have very low disk space. This may be a out of disk space in disguise. On Sat, 21 Jul 2018, 14:12 Rob Tompkins, wrote: > Looks like Jenkins timed out on checkout or something. > > > On Jul 20, 2018, at 1:08 PM, Ralph Goers > wrote: > > > > No idea. > > > > Ralph > > > >

Re: Build failed in Jenkins: Log4j 2 3.x #148

Looks like Jenkins timed out on checkout or something. > On Jul 20, 2018, at 1:08 PM, Ralph Goers wrote: > > No idea. > > Ralph > >> On Jul 20, 2018, at 9:56 AM, Gary Gregory wrote: >> >> Could this be a corrupt local repo or an out of disk space issue? >> >> Gary >> >> On Fri, Jul 20, 20

Re: Build failed in Jenkins: Log4j 2 3.x #148

No idea. Ralph > On Jul 20, 2018, at 9:56 AM, Gary Gregory wrote: > > Could this be a corrupt local repo or an out of disk space issue? > > Gary > > On Fri, Jul 20, 2018 at 10:44 AM Apache Jenkins Server < > jenk...@builds.apache.org> wrote: > >> See

Re: Build failed in Jenkins: Log4j 2 3.x #148

Could this be a corrupt local repo or an out of disk space issue? Gary On Fri, Jul 20, 2018 at 10:44 AM Apache Jenkins Server < jenk...@builds.apache.org> wrote: > See > > -- > Started by