All of lore.kernel.org
 help / color / mirror / Atom feed
* Stability of Master (not looking good)
@ 2011-01-14  7:26 Saul Wold
  2011-01-17  7:09 ` Saul Wold
  0 siblings, 1 reply; 2+ messages in thread
From: Saul Wold @ 2011-01-14  7:26 UTC (permalink / raw)
  To: poky@yoctoproject.org


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?

-- 
     Sau!

Saul Wold
Yocto Component Wrangler @ Intel
Yocto Project / Poky Build System



^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: Stability of Master (not looking good)
  2011-01-14  7:26 Stability of Master (not looking good) Saul Wold
@ 2011-01-17  7:09 ` Saul Wold
  0 siblings, 0 replies; 2+ messages in thread
From: Saul Wold @ 2011-01-17  7:09 UTC (permalink / raw)
  To: Saul Wold; +Cc: poky@yoctoproject.org

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!


^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2011-01-17  7:09 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2011-01-14  7:26 Stability of Master (not looking good) Saul Wold
2011-01-17  7:09 ` Saul Wold

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.