Re: Build Breakage

[Wu Zhou <woodzltc at cn dot ibm dot com>]

Hi Andrew,

Nice to meet you guys in Toronto!  Here are my two cents.

On Tue, 27 Jun 2006, Andrew Cagney wrote:

> Wu Zhou wrote:
> > On Sat, 24 Jun 2006, Sami Wagiaalla wrote:
> > 
> >   
> > > Hi everybody,
> > > 
> > > There has been a lot of build breakage recently. Please remember that
> > > code in cvs *must always build*... it doesnt have to work :P but it has to
> > > build.
> > >     
> > 
> > Yes.  This is very important I believe, especially for new guys who just
> > heard about frysk and want to have a try.  :-)
> > 
> > Maybe we can have some kind of policy here?
> Yes, I agree, and there is.  It's really simple:  frysk always builds; frysk's
> testsuite always passes.

I totally agree to the first one: frysk has to always build.  But in my
opinion, the testcases exist to find bug.  To expose new problem is the
value of the testcase, right? So I hold the point that we can let these
failing tests enabled.  We would like to see all frysk's testsuite pass.
But if there are anything failing, why not just let them open.  This is a
sign that there are some problem for us to resolve.  A 100 percent pass
rate might obscure our eyes.  What do you think?

The second concern I have is on the execution of the presribed policy. I 
am thinking that if we can test at least on two platforms before we 
check in the code, that will be great.

 Regards
- Wu Zhou