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

Re: Road to 1.6: XFailing tests

From: Paul Burba <ptburba_at_gmail.com>
Date: Wed, 26 Nov 2008 09:48:02 -0500

On Tue, Nov 25, 2008 at 8:56 PM, Hyrum K. Wright
<hyrum_wright_at_mail.utexas.edu> wrote:
> In preparing for the pending branch of 1.6, I took a look this afternoon at the
> current XFailing tests on trunk, compared to the XFailing tests on 1.5.x. I
> would consider any test which currently fails on trunk, expected or not, which
> doesn't fail on 1.5.x to be a demonstration of a bug. Those tests are:


Looking at just the merge tests:

> XFAIL: merge_tests.py 19: merge should skip over unversioned obstructions
> XFAIL: merge_tests.py 20: merge into missing must not break working copy
Both came back from the tree-conflicts branched marked as XFail

> XFAIL: merge_tests.py 33: merge a replacement of a directory
The fix of another bug exposed a different (existing) bug in this
test, but it doesn't appear there is any regression - see r32904 .

> XFAIL: merge_tests.py 39: conflict from merge of add over versioned file
> XFAIL: merge_tests.py 68: mergeinfo recording in skipped merge
Both came back from the tree-conflicts branched marked as XFail

> XFAIL: merge_tests.py 91: merge added subtree
New test in 1.6 for issue #1962

> XFAIL: merge_tests.py 125: merge prior to rename src existence still dels src
New test in 1.6 for issue #3324


> Some of these may be new tests in 1.6, others might just be bad expected output,
> and yet others may be regressions from 1.5. Are there any volunteers to take a
> look at the above tests and either fix them, or classify them into one of the
> above categories so that others can fix them?
> Thanks,
> -Hyrum

To unsubscribe, e-mail: dev-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: dev-help_at_subversion.tigris.org
Received on 2008-11-26 15:48:11 CET

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.