All of lore.kernel.org
 help / color / mirror / Atom feed
From: Elizabeth Flanagan <elizabeth.flanagan@intel.com>
To: poky@yoctoproject.org
Subject: Re: Master Stability
Date: Tue, 07 Dec 2010 09:44:09 -0800	[thread overview]
Message-ID: <4CFE7269.4000507@intel.com> (raw)
In-Reply-To: <4CFD94DD.7010906@intel.com>

Acked-by: Beth Flanagan

(Stands on build engineer soap box)

If at all possible, when you try to verify a fix, do a full clean build
for more than just one arch using BB_NUMBER_THREADS and PARALLEL_MAKE.
With the number of pull requests coming through, it becomes more and
more vital to verify patches prior to sending them out.

Preferably, I'd like to start seeing people add something like a
Verified-with: <build target> tag to pull requests, so we can at least
identify pulls that need more peer review than normal.

-b


On 12/06/2010 05:58 PM, Saul Wold wrote:
> 
> Folks,
> 
> We had a rash of changes that have broken master, I am trying to resolve 
> the last few breakages, which mostly are in meta-toolchain-sdk build. I 
> realized that this is not in our normal test build path.
> 
> I have fixes for most of the break (I hope), there are still a couple of 
> items that we need to address.
> 
> There is a failure for libatomics on mips, there may be a configuration 
> issue.
> 
> Please be sure to verify your builds before makeing pull requests.
> 
> 
> Thanks
> 	Sau!
> 
> 
> 
> 
> _______________________________________________
> poky mailing list
> poky@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/poky



  reply	other threads:[~2010-12-07 17:44 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 [this message]
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
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=4CFE7269.4000507@intel.com \
    --to=elizabeth.flanagan@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.