[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:30:55 CEST

On 8/9/07, Eric Gillespie <epg@pretzelnet.org> wrote:
> Kamesh Jayachandran <kamesh@collab.net> writes:
> > Shouldn't you put this test as XFail if you want to test the
> > un-implemented feature(*Not propagating the pre-revprop-change hook
> > failure*).
> No, it's not an unimplemented feature, but a regression. See
> http://svn.haxx.se/dev/archive-2007-08/0010.shtml

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
regressions or otherwise. Lieven has been reviewing all XFail tests
for every release and comparing them with previous releases, so
regressions don't go undetected.

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...



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:29:02 2007

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