[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: svn commit: r25991 - in trunk/subversion/tests/cmdline: . svntest

From: Eric Gillespie <epg_at_pretzelnet.org>
Date: 2007-08-09 21:35:11 CEST

"Erik Huelsmann" <ehuels@gmail.com> writes:

> Yes. But you already pointed that out in that e-mail. What use is
> buildbot to others if this *known* regression makes all ra_neon builds
> fail? I'm strongly against committing failing tests knowingly, for

What? Why does it make builds fail? It should only result in
this one test showing up as failing in automated test runs.
Which is as it should be, no? We don't want all lights green if
the code is known broken!

But, that's just me :). I don't object to turning this into an
XFail instead.

> I don't think a failing test is the only (or even right) way to find a
> developer to get the regression fixed. If you think a regression is to
> be fixed before the next release, you can file a P1 or P2 issue
> against the next release...


Eric Gillespie <*> epg@pretzelnet.org
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Aug 9 21:33:16 2007

This is an archived mail posted to the Subversion Dev mailing list.