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

RE: 1.6.0-rc3 up for signing/testing

From: Geoff Rowell <geoff.rowell_at_varolii.com>
Date: Mon, 2 Mar 2009 09:39:40 -0500

On Sun, Mar 01, 2009 at 12:22 PM, Paul Burba <ptburba_at_gmail.com> wrote:
> XFAIL update_tests.py 32: update wc on the root of a Windows (virtual) drive.
>
> It fails, which we expect, but triggers an SVN_ERR_ASSERT(). The fix
> for this is r36049-r36051 and r36131, which are nominated for
> inclusion in 1.6.1. This test fails without incident in 1.5.x, but I
> am able to get an abort (rather than an SVN_ERR_ASSERT which is new in
> 1.6) with 1.5.6, so this is not a regression. Also, the situation is
> fairly uncommon, you must simultaneously commit multiple WCs whose
> common parent is the root of a drive; so the workaround is simple,
> commit them individually. Given all this, I don't believe it should
> hold up the release.
>
No desire to hold up the release train, but this is rather more common than
you think. Our Windows developers build off of a "subst" K: drive. the source
tree includes externals in the top level and in the next few levels.

Committing from "K:\" triggers this.

This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the sender.

------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=462&dsMessageId=1256567
Received on 2009-03-02 15:38:26 CET

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.