Failed tests in KDevelop

[Andreas Pakulat]

On 20.05.09 09:56:28, Amilcar do Carmo Lucas wrote:
> On Sunday 26 April 2009 02:35:01 Amilcar do Carmo Lucas wrote:
> > 90% tests passed, 7 tests failed out of 71
> >
> > The following tests FAILED:
> >           8 - veritas-unit-stubcreation (Failed)
> >          20 - cmake-cmakecondition (Failed)
> >          21 - cmakeduchaintest (Failed)
> >          22 - cmakeprojectvisitortest (Failed)
> >          29 - gdbtest (Failed)
> >          49 - gcov-mem-reportwidget (Failed)
> >          71 - qtest-mem-qtestrunnertest (Failed)
> >
> > Is this normal ?
> 
> 
> One month has passed and only one test got fixed:
> >          20 - cmake-cmakecondition (Passed)
> So how about disabling failing tests ? That way it would be easier to spot 
> regressions.

No it would not, because failing tests means there are regressions already.
Either the tests are not useful, which means they should be removed, or
they are useful which means they should be fixed.

However, as you can see, people's time is limited and the tests you've
listed are all in currently under-maintained or even unmaintained areas.

Andreas

-- 
You will be awarded some great honor.