> -----Original Message-----
> From: Paul Burba [mailto:ptbu...@gmail.com]
> Sent: maandag 14 januari 2013 22:20
> To: Subversion Development
> Cc: Stefan Sperling; Julian Foad; Bert Huijben
> Subject: 1.8 Release Status : Test Review Task Update
>
> Re the roadmap item "Test Review - Determine which XFail and WIP tests
> should remain so, and which need to be fixed before release." We are
> almost done, only 5 Xfailing tests remain that are either associated
> with a 1.8.0 issue or no issue. We currently have no WIP issues.
> Details below.
>
>
> Ignoring tests with associated issues with the 1.8-consider milestone
> we have only one XFailing test associated with an issue with the 1.8.0
> milestone (and it appears Julian is actively working on this, at least
> it's assigned to him and marked as started):
>
> LISTING: merge_tests.py
> Test # Mode Test Description
> Issue#(Target Mileston/Assigned To)
> ------ ----- ----------------
> 131 XFAIL merge binary file with keywords
> #4221(1.8.0/julianfoad)
>
> Julian - What's the status on this? You still working on it? Is it
> really a blocker for 1.8.0?
>
> ~~~~~
>
> There are still three XFailing tests with no associated issue:
>
> LISTING: update_tests.py
> Test # Mode Test Description
> ------ ----- ----------------
> 60 XFAIL update locally moved dir with leaf del
> 61 XFAIL update locally moved dir with edited leaf del
> 62 XFAIL update locally moved dir with incoming file
>
> These three have previously been discussed (and don't appear to be
> 1.8.0 blockers):
>
> On Thu, Dec 13, 2012 at 7:10 PM, Paul Burba <ptbu...@gmail.com> wrote:
> > On Tue, Nov 6, 2012 at 3:37 PM, Paul Burba <ptbu...@gmail.com> wrote:
> >> On Sat, Nov 3, 2012 at 9:33 AM, Stefan Sperling <s...@elego.de> wrote:
> >>> On Fri, Nov 02, 2012 at 06:00:52PM -0400, Paul Burba wrote:
> >>>> These six XFailing upate tests are all part of this effort correct?
> >>>>
> >>>> 61 XFAIL update locally moved dir with leaf del
> >>>> 62 XFAIL update locally moved dir with edited leaf del
> >>>> 63 XFAIL update locally moved dir with incoming file
> >>>> 64 XFAIL update locally moved dir with incoming dir
> >>>
> >>> I believe the above date back to 1.6. They verify that tree
> >>> conflict detection works correctly.
> >>>
> >>> I might have changed them since 1.7 was branched to account
> >>> for some changes I made. I'll look into that next week.
> >
> > Ping. You had any chance to take a look at these?
>
> Stefan - Anything to add re these tests?
>
> ~~~~~
>
> Lastly, we have one XFailing C-test that Bert added last week:
>
> C:\SVN\src-trunk-2>Debug\subversion\tests\libsvn_wc\op-depth-test.exe
> 45
> ..\..\..\subversion\tests\libsvn_wc\op-depth-test.c:5391: (apr_err=200006)
> ..\..\..\subversion\tests\libsvn_wc\op-depth-test.c:232: (apr_err=200006)
> svn_tests: E200006: expected {1, C2/f, normal, copyfrom ^/A2/B/C/f@2,
> moved-here}; found {1, C2/f, normal, copyfrom ^/A/B/C/f@1, moved-here}
> ..\..\..\subversion\tests\libsvn_wc\op-depth-test.c:232: (apr_err=200006)
> svn_tests: E200006: expected {1, C2, normal, copyfrom ^/A2/B/C@2,
> moved-here}; found {1, C2, normal, copyfrom ^/A/B/C@1, moved-here}
> XFAIL: op-depth-test.exe 45: nested_move_commit
>
> Bert - Is this a blocker for 1.8.0?
I think it is. (It is part of the move work)
The nested move makes the database invalid after committing.
The commit operation should update the move origin (and revision, etc.)
Bert
