Hello,

On Mon, 28 Jan 2013 16:44:32 +0000
Matthew Gretton-Dann <[email protected]> wrote:

[]
> > 1. tcserver01x5, which belongs to x86_64-heavy queue, and
> > apparently is a VM hosted in lava lab, hangs for 16 days, with a
> > dozen jobs in backlog. "tcserver01x5" didn't ping for me from
> > gateway, but "tcserver01" does, so maybe it's live but has some
> > issues.
> 
> tcserver01x5 seems to have appeared recently (this month) - I didn't
> put it there, so I don't know what exactly it is.
> 
> > 2. a9hf-daily has single active machine, tcpanda11, so that's in
> > permanent, and probably growing, backlog.
> 
> So 'daily' is the 'do this if you've nothing better to do' queue.
> Items appear at the rate of once a day, and get purged if not done
> after two weeks.  Around release weeks this queue gets really big as
> there are many builds with higher priority spawned.

Ah, yes, I remember Michael mentioning something like that too, good to
know.

> 
> > I understand that leveraging LAVA builds is probably the best way to
> > resolve the issue, and I'm currently validating and tweaking those
> > builds (but I'm not sure if build image as was provided by Michael
> > is hardfloat or not, and how to go about adding missing one).
> 
> So in fact the daily queues are probably the best queues to initially
> move to being pure Lava queues, as they are not currently business
> critical for the working group (but may soon be).

Ok, let's go that route. Step by step, currently I'm validating that
LAVA builds match native and sane otherwise.

> 
> Sorry to be naive - if by build image you mean filesystem then uname
> -a should tell you whether you have a Hardfloat
> (arm-none-linux-gnueabihf) or soft-float (arm-none-linux-gnueabi)
> system, and you should be able to multi-arch the system to get hold of
> soft-float binaries.

I'm not much knowledgeable of hardfloat and not sure if it requires
kernel support of fully user-space thing. I added "uname -a" to build
process and it gives:

Linux ursa4 3.5.0-r1 #1 SMP PREEMPT Tue Aug 14 17:16:00 NZST 2012
armv7l armv7l armv7l GNU/Linux

I don't see anything special there (should hardfloat be armv7hl?).
However, CBuild itself classifies it as hard-float, based on URL for
results:
http://cbuild.validation.linaro.org/build/gcc-linaro-4.7-2013.01/logs/armv7l-precise-cbuild456-lava-cortexa9hfr1/
So, I wonder if that's correct or it's another mixup with LAVA builds,
like hostname. I'll look into that, but appreciate your checking it too.


> 
> Thanks,
> 
> Matt
> 
> --
> Matthew Gretton-Dann
> Linaro Toolchain Working Group
> [email protected]



-- 
Best Regards,
Paul

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

_______________________________________________
linaro-validation mailing list
[email protected]
http://lists.linaro.org/mailman/listinfo/linaro-validation

Reply via email to