An Update:

Every xfailing test now has an issue associated with it except for these three:

1) fs-test.exe 18 'merging commit'
As explained in the test, "needs to be written to match new merge()
algorithm expectations" and here,
http://svn.haxx.se/dev/archive-2011-02/0044.shtml, this is not a 1.7
blocker.

2) switch_tests.py 38 'copy directory with switched subdir'
Thread: http://svn.haxx.se/dev/archive-2011-02/0360.shtml
Bert is going to look at this.

3) patch_tests.py 29 'patch doesn't append newline to properties'
Being discussed on http://svn.haxx.se/dev/archive-2011-02/0350.shtml

Ignoring those three for a moment, as of today we have 52 xfailing
tests, of those there are 21[1] which have no milestone or
1.7.0/1.7-consider milestones.

I just committed some test suite tweaks in r1071809 which allows us to
filter the listing of tests to those which have an associated issue
with a given target milestone.  This means that the
'/subversion/trunk/notes/xfail-status' is *almost* defunct...I won't
delete it just yet, until we can use the new --milestone-filter option
fully on linux and until there is a way to associate xfailing C tests
with issues.

Anyhow, these are what we need to focus on:

C:\SVN\src-trunk>win-tests.py --list
--milestone-filter="(1\.7.*)|(---)" --mode-filter xfail
--log-to-stdout
<SNIP>
LISTING: copy_tests.py
Test #  Mode   Test Description
------  -----  ----------------
  24    XFAIL  wc to wc copy with deleted=true items
[#2101(unscheduled),#2020(unscheduled),#3776(1.7.0)]
  80    XFAIL  commit only top of copy; check child behavior
[#3699(1.7-consider)]
  89    XFAIL  copy mixed-rev and delete children [#3314(---)]
  91    XFAIL  copy, delete child, revert copy [#3784(1.7.0)]

LISTING: lock_tests.py
Test #  Mode   Test Description
------  -----  ----------------
  34    XFAIL  unlock file locked by other user [#3801(1.7-consider)]

LISTING: merge_tests.py
Test #  Mode   Test Description
------  -----  ----------------
  64    XFAIL  merge target with non inheritable mergeinfo
[#2970(blue-sky),#3642(1.7.0)]
  75    XFAIL  merge added subtree [#1962(1.7-consider)]

LISTING: revert_tests.py
Test #  Mode   Test Description
------  -----  ----------------
  23    XFAIL  non-recursive revert after delete [#3783(1.7.0)]

LISTING: switch_tests.py
Test #  Mode   Test Description
------  -----  ----------------
  10    XFAIL  switch a file to a dir and back to the file [#1532(1.7-consider)]

LISTING: tree_conflict_tests.py
Test #  Mode   Test Description
------  -----  ----------------
   8    XFAIL  up/sw dir: add onto add [#3314(---)]
  14    XFAIL  merge dir: del/rpl/mv onto not-same [#3150(1.7.0)]
  20    XFAIL  issue #3608: reverting an add onto add conflict [#3608(---)]
  21    XFAIL  lock status update shouldn't flag tree conflict
[#3525(1.7-consider),#3533(unscheduled)]

LISTING: update_tests.py
Test #  Mode   Test Description
------  -----  ----------------
  47    XFAIL  tree conflicts 2.3: skip on 2nd update [#3329(1.7-consider)]
  53    XFAIL  verify update of deleted locked files [#3525(1.7-consider)]
  57    XFAIL  update with file lock & keywords property set [#3471(---)]
  58    XFAIL  update a nonexistent child of a copied dir [#3807(1.7.0)]

LISTING: upgrade_tests.py
Test #  Mode   Test Description
------  -----  ----------------
   9    XFAIL  3x same wc upgrade 1.4.6 test [#3811(1.7.0)]
  10    XFAIL  3x same wc upgrade 1.6.12 test [#3811(1.7.0)]
  13    XFAIL  check status delete and delete --keep-local [#3808(1.7.0)]


[1] There's on C test too: parse-diff-test.exe 4 XFAIL 'test badly
formatted git diff headers': Issue #3809

Paul

Reply via email to