jenkins really broken right now
paul.sokolovsky at linaro.org
Wed Mar 28 11:11:06 UTC 2012
On Wed, 28 Mar 2012 13:05:21 +0300
Paul Sokolovsky <Paul.Sokolovsky at linaro.org> wrote:
> On Tue, 27 Mar 2012 17:06:53 -0600
> John Rigby <john.rigby at linaro.org> wrote:
> > On Tue, Mar 27, 2012 at 4:55 PM, Loïc Minier
> > <loic.minier at linaro.org> wrote:
> > > On Tue, Mar 27, 2012, John Rigby wrote:
> > >> Looks like initial git clones always fail. I tried a simple job
> > >> that just trys to run git and it fails.
> > >
> > > Alexander noticed too; new ci.linaro.org setup was launching jobs
> > > which were actually pointing at old ci.linaro.org setup as web
> > > proxy. When the old instance was shut down, it exposed the
> > > problem. Problem is that new instance doesn't have squid
> > > installed/configured. We need to restore the config and any other
> > > missing bits.
> > >
> > My jobs seem to be working again, I guess without the proxy for now
> > but working none the less. Thanks to all for fixing this.
> But well, new instance couldn't automatically use squid on the old -
> old had his IP/domain name changed, so stale config wouldn't explain
> it. I also thought that Loic might have restarted the old instance,
> bit it wasn't, so doesn't explain why builds went thru. So, maybe
> it's not squid after all. We'll be looking into the issue immediately.
Ok, it turns out that the cache was accessed as internal EC2 IP,
"http://ip-10-195-115-143.ec2.internal:3128". So, mystery off, the issue
fully understood and confirmed.
Linaro.org | Open source software for ARM SoCs
Follow Linaro: http://www.facebook.com/pages/Linaro
http://twitter.com/#!/linaroorg - http://www.linaro.org/linaro-blog
More information about the linaro-dev