David Glasser wrote:
> Did people run the new tests on the branch before voting for backport?
> It seems to depend on the new "testing exit codes" stuff and fails
> for me.
> Or am I the only one seeing this?
No, the buildbot is also showing problems on all platforms. Looks like
update test 44 is failing.
[..]
>> Modified: branches/1.5.x/subversion/tests/cmdline/update_tests.py
>> URL: http://svn.collab.net/viewvc/svn/branches/1.5.x/subversion/tests/cmdline/update_tests.py?pathrev=30838&r1=30837&r2=30838
>> ==============================================================================
>> --- branches/1.5.x/subversion/tests/cmdline/update_tests.py Tue Apr 29 09:08:33 2008 (r30837)
>> +++ branches/1.5.x/subversion/tests/cmdline/update_tests.py Tue Apr 29 09:38:31 2008 (r30838)
>> @@ -3814,6 +3814,45 @@ interactive-conflicts = true
>> '-r1', wc_dir)
>>
>>
>> +#----------------------------------------------------------------------
>> +
>> +
>> +def update_uuid_changed(sbox):
>> + "update fails when repos uuid changed"
>> +
>> + def wc_uuid(wc_dir):
>> + "Return the UUID of the working copy at WC_DIR."
>> +
>> + exit_code, output, errput = svntest.main.run_svn(None, 'info', wc_dir)
>> + if errput:
>> + raise svntest.verify.SVNUnexpectedStderr(errput)
>> +
Removing this exit_code should be sufficient.
@David: I see you already proposed a fix for backport, I'll add my vote.
Lieven
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: dev-help_at_subversion.tigris.org
Received on 2008-04-30 09:21:57 CEST