This looks to be this issue https://issues.jenkins-ci.org/browse/JENKINS-22734 or https://issues.jenkins-ci.org/browse/JENKINS-22734 but I don't have access to build slaves to actually get down and dirty with logs. Either way, our Jenkins setup is pretty old, latest is 1.572 and ours is 1.455. I'm going to talk to a few people here and see about updating our Jenkins setup and any other work we need to do infra side to get this issue fixed. I'll report back with anything I find so we can get a gameplan going.
Julien On Fri, Jul 11, 2014 at 6:08 PM, Konstantin Boudnik <[email protected]> wrote: > Thanks for checking it out, Mark. I've tried to untangle it last night, but > without much success. The most weird part is that cleaning up build queue > and > restarting to the trunk-all job grinds to the same halt every time ;( > > Cos > > On Fri, Jul 11, 2014 at 10:29AM, Mark Grover wrote: > > Maybe, it's archiving the artifacts on the Jenkins master? (sorry, don't > > understand much about how the Jenkins artifact archiver works, I will > poke > > more). > > > > I don't have access to it, can someone with access to Jenkins master > check > > if life is good on it? > > > > > > On Fri, Jul 11, 2014 at 10:25 AM, Mark Grover <[email protected]> wrote: > > > > > Yeah, I noticed that too. Looking into it, ssh'ing into the slave, disk > > > space looks fine. I am trying to understand where the Jenkins archiver > is > > > archiving to, maybe that thing ran out of space... > > > Mark > > > > > > > > > On Fri, Jul 11, 2014 at 10:24 AM, Julien Eid <[email protected]> > > > wrote: > > > > > >> http://bigtop01.cloudera.org:8080/job/Bigtop-trunk-Hadoop/ > > >> > > >> Fedora 18 box is blocking jobs from running for the past two days. > > >> > > >> > http://bigtop01.cloudera.org:8080/job/Bigtop-trunk-Sqoop/label=fedora18/624/console > > >> Stuck on archiving Sqoop artifacts. > > >> > > > > > > >
