On 12 December 2012 05:55, Andy Doan wrote:
> On 12/11/2012 05:57 AM, Paul Sokolovsky wrote:
>>
>> Hello,
>>
>> As discussed and OKed today on Toolchain release pre-talk meeting,
>> Infrastructure would like to request "cbuild" user access on
>> toolchain64 machine. It would definitely help during
On 26 July 2012 08:09, Andy Doan wrote:
> Loic brought up some good points about EC2 and I'll let that thread continue
> to discuss those merits. However, there are some things I can still discuss
> that are needed for LAVA regardless but also happen to fit nicely with
> Michael's goals.
>
> I spo
On 25 July 2012 23:30, Loïc Minier wrote:
> Thanks for the notes and sorry for missing the meeting (was actually
> around but thought it was a full-day event reminder that was firing
> rather than a real meeting, and didn't see the meeting in the daily
> google calendar email! sorry).
>
> I'm fin
I'd like to move the cbuild infrastructure out of my home office and
domains and into the validation lab. That makes things one step
cleaner than the current setup and one step closer to hooking things
into LAVA.
There's more terse notes at:
https://wiki.linaro.org/MichaelHope/Sandbox/CBuildMove
On 12 June 2012 04:43, Joey STANFORD wrote:
> Sweet thanks.
>
> One more task for you sir which should be easy and straightforward
>
> Nuke your sandbox. :-) You have a bunch of awesome stuff hidden away
> that really should be under a better location in the wiki. For
> example, this cbuil
One action from Connect was to write up what cbuild is and how it
works. I tidied up the old writeup at:
https://wiki.linaro.org/MichaelHope/Sandbox/cbuild
-- Michael
___
linaro-validation mailing list
[email protected]
http://lists.l
On 9 May 2012 12:14, Michael Hudson-Doyle wrote:
> On Tue, 8 May 2012 15:56:27 +1200, Michael Hope
> wrote:
>> On 7 May 2012 20:10, Zygmunt Krynicki wrote:
>> > Hi.
>> >
>> > We'll see some beta deployments this week. I have not tried doing any
>
chpad.net/lava-core/+spec/dispatcher-transition-plan
OK. Do you have documentation or a specification you're working to?
Does your plan cover my needs or something close to it?
> Thanks
> ZK
>
>
> On Mon, May 7, 2012 at 5:40 AM, Michael Hope wrote:
>> Hi there. We
Hi there. We'd like to run a Fast Model in the validation lab for KVM
testing. Is there a blueprint for this? What's the status?
Paul and I discussed a rough plan a few months ago. It was along the lines of:
* A x86 machine as the Fast Model host
* An emulated vexpress-a15 as the KVM host
*
On 29 March 2012 04:20, Paul Larson wrote:
>
> On Wed, Mar 28, 2012 at 10:03 AM, Andrew Stubbs
> wrote:
>>
>> On 28/03/12 03:26, Michael Hope wrote:
>>>
>>> Hi there. The GCC build time is approaching 24 hours and our five
>>> Panda boards can&#x
On 29 March 2012 00:02, Andrew Stubbs wrote:
> On Tue 27 Mar 2012 22:03:45 BST, Michael Hope wrote:
>>
>> The PandaBoard auto builders are having a hard time keeping with
>> longer build and test times of 4.7 and the re-enabled libstdc++ tests.
>> For reference, here
Hi there. The GCC build time is approaching 24 hours and our five
Panda boards can't keep up. Sounds like a good time to LAVAise the
toolchain build process a bit more...
Mike Hudson and I talked about doing a hybrid LAVA/cbuild as a first
step where LAVA manages the boards and cbuild does the b
The PandaBoard auto builders are having a hard time keeping with
longer build and test times of 4.7 and the re-enabled libstdc++ tests.
For reference, here's how much each step costs:
Bootstrap GCC with C, C++, Fortran, and Obj-C: 9 hours
Test GCC: 9.5 hours
Test libstdc++: 4.4 hours
Test libgomp
I've added a new job called 'porter' which reserves the first tcpanda
that comes free. This can be used to reproduce a bug or benchmark
result against an existing binary build.
For example, say you want to see if a fault exists on recent trunk:
* Go to http://ex.seabright.co.nz/helpers/buildlog/
The Validation lab is shifting to a new location this week so I've
started a graceful shutdown of the tcpanda boards. Merge requests
will continue to queue and run on x86 but will back up until the lab
comes online at the end of this week. If the backlog gets too big
then I'll re-enable an ursa b
On Tue, Mar 6, 2012 at 6:54 AM, Andy Doan wrote:
>> I don't think that's a problem. In fact, what I'm suggesting is to
>> simply have it available as a download from our NAS system in the lab,
>> that is behind the firewall and not exposed. You'll need to get us to
>> put the file there, but then
16 matches
Mail list logo
