[oe] testing 2010-12-10 (wiki, results, bluez-libs)

[Cliff Brake]

On Wed, Dec 15, 2010 at 9:43 AM, Tom Rini <tom_rini at mentor.com> wrote:
> On 12/15/2010 12:51 AM, Frans Meulenbroeks wrote:
>>
>> Dear all,
>>
>> I just wanted to update the testing table with my entries and I
>> noticed two (possibly related) things.
>> - no other entries for 2010-12-10 are there yet (and it is already
>> wednesday)
>
> I haven't updated the stuff we're building since just about everything
> failed due to the gcc issue Khem fixed in
> 2c8570552549da2e11428d08b2bc08849cac39b1.  This is why I sometimes wonder if
> it would be desirable to cherry-pick a few things in to the testing-next
> branch.

One of my concerns is coordinating with all the people doing testing
if we start committing to the testing-next branch.  How do we know who
restarted builds, etc.  I guess we could assume the cherry-picked
changes would be minor enough that people who have already finished
builds would not need to re-build.

At this point I'm just more inclined if the weekly testing branch
crashes and burns horribly to just throw away that week, and focus on
getting things fixed in the master for next week.  Its not perfect,
but with so many people participating, it seems like we need to keep
it as simple as possible.  But, keep the ideas flowing, and perhaps
something better will emerge.

Thanks,
Cliff

-- 
=================
http://bec-systems.com