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

Re: atomic-revprop: help tracking down ra_serf failures

From: Daniel Shahaf <d.s_at_daniel.shahaf.name>
Date: Fri, 10 Sep 2010 12:49:20 +0300

Lieven Govaerts wrote on Fri, Sep 10, 2010 at 07:46:55 +0200:
> On Fri, Sep 10, 2010 at 2:12 AM, Daniel Shahaf <d.s_at_daniel.shahaf.name> wrote:
> > [ I'm only talking about the ra_serf tests in this email ]
> >
> > When I build the atomic-revprop branch against serf r1408, I see that:
> >
> > * diff_tests 24 29 (and many others [1]) fail with HEAD of the branch.
> >    (IIRC these two failures persist if I switch to serf ^/branches/0.4.x_at_HEAD.)
> > * diff_tests 24 29 fail with r983269 reverted. (test output attached)
>
> In this log file, the only difference I see is that the output of
> 'iota' and 'A' are in reverse order in expected versus actual output.
>

How do you see "in a reverse order"? This is what I see:

[[[
DIFF STDOUT (unordered):
--- EXPECTED STDOUT
+++ ACTUAL STDOUT
@@ -1,17 +1,8 @@
-Index: A
-===================================================================
---- A (revision 2)
-+++ A (revision 1)
-
-Property changes on: A
-___________________________________________________________________
-Deleted: dirprop
-## -1 +0,0 ##
--r2value
 Index: iota
 ===================================================================
 --- iota (revision 2)
 +++ iota (revision 1)
+
 Property changes on: iota
 ___________________________________________________________________
 Deleted: fileprop
]]]

which means that the entire diff for "A" has disappeared.

> Isn't this just a question of ra_serf not guaranteeing depth-first output?
>

No. The above paste indicates that the expected output is already
marked "unordered" and that the output for A's dirprop is missing.

> Lieven
> [..]
Received on 2010-09-10 11:53:39 CEST

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.