Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[wtp-releng] More on JUnit's policy and principles


>  I've got to voice my disapproval of commenting out this failing test.

Lawrence, perhaps you mean you object to us declaring a  build this week if this problem is not fixed? If so, please let us know.

But otherwise, the failing JUnit's are first and foremost for committers to know there's a problem. Once known, a bug is open,
folks begin to work on it with a priority measured right along with every other bug, but if it can not be fixed right away, there is no further
advantage to displaying the failing JUnit's. And, it's my belief it's actually a bad practice to leave "known
failing tests" in the suite, since it teaches everyone to ignore nonzero numbers, since they are often nonzero.  

I requested this action the status call, so you might not have known the whole story behind the brief summary,
if you were not on the status call.

I definitely agree with you this problem is serious and needs to be fixed. My own opinion is we do not need to wait until the "ibm.com" site is
fixed for us to declare this RC, but if you and other committers think we should wait for ibm.com to fix their site, then I'd want to know that, and
the details of why.

Thanks

Back to the top