All of lore.kernel.org
 help / color / mirror / Atom feed
From: Saul Wold <saul.wold@intel.com>
To: "Stewart, David C" <david.c.stewart@intel.com>
Cc: "<poky@yoctoproject.org>" <poky@yoctoproject.org>
Subject: Re: Master Stability
Date: Tue, 07 Dec 2010 17:16:37 -0800	[thread overview]
Message-ID: <4CFEDC75.6060207@intel.com> (raw)
In-Reply-To: <B27EBC40D200ED48A3F4CC2EBEABAE0B25BBC511D0@orsmsx501.amr.corp.intel.com>

On 12/07/2010 05:06 PM, Stewart, David C wrote:
>> From: poky-bounces@yoctoproject.org [mailto:poky-
>> bounces@yoctoproject.org] On Behalf Of deVries, Alex
>> Sent: Tuesday, December 07, 2010 1:27 PM
>>
>> Does Intel have a plan to expand the amount of hardware used for
>> automated builds? It would give us a lot more build coverage and help
>> with overall build quality.
>
> New server has arrived, waiting to be integrated into the hosted data center.
>
> I'm trying to get a bead on whether we need more, and can try to budget this for next quarter if the new one isn't enough.
>
We will need new hardware next qtr, maybe even soon, as we start to 
enable more targets and add support for swabber on a semi-regular basis 
our cycles are going to be greatly diminished.

We should really look into getting a large multi-core machine to help.

Sau!


  _______________________________________________
> poky mailing list
> poky@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/poky
>



  reply	other threads:[~2010-12-08  1:16 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-07  1:58 Master Stability Saul Wold
2010-12-07 17:44 ` Elizabeth Flanagan
2010-12-07 18:43   ` Joshua Lock
2010-12-07 18:54     ` Scott Garman
2010-12-07 21:27       ` deVries, Alex
2010-12-08  1:06         ` Stewart, David C
2010-12-08  1:16           ` Saul Wold [this message]
2010-12-08 12:14       ` Joshua Lock
2010-12-08  2:59 ` Tian, Kevin

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4CFEDC75.6060207@intel.com \
    --to=saul.wold@intel.com \
    --cc=david.c.stewart@intel.com \
    --cc=poky@yoctoproject.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.