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

Re: expected failures shouldn't raise alarms

From: Karl Fogel <kfogel_at_newton.ch.collab.net>
Date: 2002-08-22 20:34:05 CEST

Branko Čibej <brane@xbc.nu> writes:
> At least one test FAILED, checking c:\Home\brane\src\svn\repo\tests.log
> Failed tests:
> FAIL: getopt_tests.py 7: run svn help bogus-cmd
> Unexpected passes:
> XPASS: getopt_tests.py 1: run svn with no arguments
> vs.
>
> At least one test FAILED, checking c:\Home\brane\src\svn\repo\tests.log
> XPASS: getopt_tests.py 1: run svn with no arguments
> FAIL: getopt_tests.py 7: run svn help bogus-cmd
> I'll only commit one of them. I'm not going to change the output
> based on test `id -u` = "kfogel". :-)

Oh, I prefer the latter, but only mildly. If XPASS is really a
tradition, that means there's less point explaining it in the output.

But if you prefer the other one, that's fine too.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Aug 22 20:52:59 2002

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.