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

Re: Test Failure (update_tests) over ra_dav on Mac OS X

From: Christian Schaffner <chris01_at_users.sourceforge.net>
Date: 2004-07-19 21:16:17 CEST

On 19.07.2004, at 19:36, Greg Hudson wrote:

> On Mon, 2004-07-19 at 13:11, Ben Collins-Sussman wrote:
>> This test failure disturbs me. I understand that our testsuite
>> doesn't
>> compensate for different client/server versions. I understand that if
>> we added a new test that tested for a specific bugfix or new feature
>> in
>> 1.1, that such a test would fail against a 1.0 server. That makes
>> sense. But we're talking about a very old test, update_tests.py #15.
>> And it's out of 22 tests. Why is this very old test failing? Why is
>> everything OK? Did it used to be XFAIL in 1.0?
> The transactionless reporter calls set_target_revision when given the
> inputs in update_tests 15, while the old reporter did not. So, with a
> new server, the client outputs "Updated to revision 3" instead of
> "Update complete". So the test case was adjusted accordingly, causing
> it to succeed with a new server and fail with an old one.

Yes, i can confirm this. I got this error message against a 1.0.5

CMD: svn "up" "working_copies/update_tests-15/A/D/G" "--config-dir"
clients/cmdline/local_tmp/config" <TIME = 0.765966>
D working_copies/update_tests-15/A/D/G
Updated to revision 3.
D working_copies/update_tests-15/A/D/G
Update complete.
FAIL: update_tests.py 15: another "hudson" problem: updates that delete

So i re-ran the tests against a 1.1.0-rc1 server and everything went

Thanks for the help,

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Jul 19 21:16:38 2004

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.