From: Elizabeth Flanagan <elizabeth.flanagan@intel.com>
To: "yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: [Bug 552] autobuild missing the non-x86 realboard images
Date: Tue, 07 Dec 2010 14:00:18 -0800 [thread overview]
Message-ID: <4CFEAE72.1030401@intel.com> (raw)
In-Reply-To: <20101207212853.4282620F48496@mail.opensource.intel.com>
I wanted to give people a heads up about the addition of a few more
targets to the nightly build and how they'll effect the nightly (and our
overall efficency).
This bug asks for the addition of a few targets:
arm: beagleboard: poky-image-sato, poky-image-minimal, poky-image-sdk
powerpc: mpc8315e-rdb: poky-image-minimal
mips: routerstationpro: poky-image-minimal
I'm going to put these into nightly after the current build is done, but
I want to make people aware of a few things.
First, our build times have been between 26 and 31 hours over the past
month. Adding these builds will increase that time. Depending on how
long this extends the total build time will depend on how big of an
effect it has.
It may also introduce new failures to the nightly which will need to be
dealt with. I know it doesn't mean much for stability since the targets
already are in master and just aren't build built, but what it does mean
is that someone needs to QA these targets.
So, like I said, I'll have this in when our next nightly kicks off. If
folks have any concerns over this, let me know before #141 finishes up.
-b
next parent reply other threads:[~2010-12-07 22:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-552-84@http.bugzilla.pokylinux.org/>
[not found] ` <20101207212853.4282620F48496@mail.opensource.intel.com>
2010-12-07 22:00 ` Elizabeth Flanagan [this message]
2010-12-08 1:12 ` [Bug 552] autobuild missing the non-x86 realboard images Bruce Ashfield
2010-12-08 8:32 ` Xu, Jiajun
2010-12-08 18:57 ` Elizabeth Flanagan
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=4CFEAE72.1030401@intel.com \
--to=elizabeth.flanagan@intel.com \
--cc=yocto@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.