From: Saul Wold <sgw@linux.intel.com>
To: Saul Wold <sgw@linux.intel.com>
Cc: "poky@yoctoproject.org" <poky@yoctoproject.org>
Subject: Re: Stability of Master (not looking good)
Date: Sun, 16 Jan 2011 23:09:37 -0800 [thread overview]
Message-ID: <4D33EB31.6060502@linux.intel.com> (raw)
In-Reply-To: <4D2FFAB8.4000506@linux.intel.com>
On 01/13/2011 11:26 PM, Saul Wold wrote:
>
> Folks,
>
> Based on what I am seeing on both local builds and on the autobuilder, I
> have to recommend that we stop making changes to master until we can
> stabilize it.
>
> We need to start getting the builds green so that we can know where we
> are going into the final days of M3 and have a build that works.
>
> We are getting closer, but there are definitely still some problem
> areas, as example, the distro-testing which has very little change
> failed to build eglibc.
>
> So, I recommend that we only make changes that directly address the
> failures we currently have until we can resolve the failures and then
> work to ensure that any new items pulled into master are well tested!
>
> I know this will slow things down, but we need to get stability happening.
>
> Thoughts?
>
Thanks everyone, things are now looking much better, we almost have
green nightlies, basically 1 sanity test failure which maybe the time
out issue.
I am working on testing the current set of changes that are queue,
including the kernel/systemtap change, the X Update and a few others
that have been requested in the last couple of days. Once that testing
is completed, RP or I will pull them into master.
Thanks to everyone for their help and understanding.
Sau!
prev parent reply other threads:[~2011-01-17 7:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-14 7:26 Stability of Master (not looking good) Saul Wold
2011-01-17 7:09 ` Saul Wold [this message]
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=4D33EB31.6060502@linux.intel.com \
--to=sgw@linux.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox