> -----Original Message-----
> From: Lieven Govaerts [mailto:firstname.lastname@example.org]
> Sent: Thursday, May 17, 2007 7:35 PM
> To: Paul Burba
> Cc: David Glasser; D.J. Heap; David Anderson; SVN Dev
> Subject: Re: Subversion 1.4.4 tarballs up for testing/signing
> Paul Burba wrote:
> > I also hang on svnadmin test 4 (empty_date) with 1.4.4.
> The same test
> > passes on trunk however.
> > So something has changed in the test suite architecture,
> but I can't
> > figure out what.
> > lgo - I'm cc:ing you in the hope you might know what
> changed with the
> > test suite to cause this, if anyone knows off the top of their head
> > it's probably you.
> On trunk the pristine repository is now created at the start
> of each testsuite, so in this case at the beginning of
> svnadmin_tests.py. While importing the greek tree in the
> pristine repository the credentials are used and cached. See
> svntest/actions.py setup_pristine_repository().
> On the 1.4.x branch, the pristine repository is created in
> svntest/actions.py guarantee_greek_repository(), but only for
> the first test case in the suite that's needing it.
> guarantee_greek_repository() is called in sbox.build(), which
> in svnadmin_tests.py is only called in the 5th test.
> I don't think it's a good idea to trust on cached credentials
> while running tests, so I support any fix which explicitly
> adds user & pwd to calls to svn.exe or svnadmin.exe.
I started a separate thread re cached credentials in the test suite.
The question at hand is what to do about 1.4.4:
* Apply Dave's fix for the test to trunk and backport (seems kinda silly
since trunk doesn't require it).
* Apply it directly to 1.4.x (totally bogus?)
* Have testers manually apply it to the 1.4.4 RC, run the tests, and
state that they did so when providing their sigs (violates our testing
process at bit, but can't we be flexible?)
To unsubscribe, e-mail: email@example.com
For additional commands, e-mail: firstname.lastname@example.org
Received on Fri May 18 17:07:07 2007