=?UTF-8?B?QnJhbmtvIMSMaWJlag==?= <brane@xbc.nu> writes:
> cmpilato@collab.net wrote:
>
> >I ran fs-tests today for the first time in a long while, I part of the
> >output was as follows:
> >
> > PASS: lt-fs-test 19: fetch the youngest revision from a filesystem
> > PASS: lt-fs-test 20: basic commit
> > PASS: lt-fs-test 21: copying and tracking copy history
> > subversion/tests/libsvn_fs/fs-test.c:2739: (apr_err=200006, src_err=0)
> > svn: Test failed
> > svn: XFAIL
> > XFAIL: lt-fs-test 22: linking, so no copy history
> > PASS: lt-fs-test 23: merging commit
> > PASS: lt-fs-test 24: commit datestamps
> >
> >I can't tell by looking at this if 22 was supposed to fail and passed,
> >or if it was supposed to fail and failed, or ...
> >
> It's an eXpected FAILure. This flag is set on tests that tickle known
> bugs. When the bug is fixed, the XFAIL turns into an XPASS -- an
> uneXpected PASS. XPASSes are listed in the test run summary along with
> any FAILs, so that you know when to remove the XFAIL flag from the
> test.
Okey dokey. Just didn't realize we were printing the error output on
XFAILs.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Oct 4 01:29:27 2002