Re: Stability of Master (not looking good)

[Saul Wold <sgw@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!