[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: Erik Huelsmann <ehuels_at_gmail.com>
Date: 2007-08-09 21:37:18 CEST

On 8/9/07, Eric Gillespie <epg@pretzelnet.org> wrote:
> "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

I'm sorry I meant "make ra_neon builds fail the tests". The PASS vs
FAIL subject headers trigger (at least for me) whether I should look
in a test result mail. If they all say FAIL, that doesn't work

> 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...
> http://subversion.tigris.org/issues/show_bug.cgi?id=2861




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:35:26 2007

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