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

Re: tree-conflicts: current branches.

From: Neels J Hofmeyr <neels_at_elego.de>
Date: Wed, 26 Nov 2008 05:35:44 +0100

Greg Stein wrote:
> On Nov 25, 2008, at 5:21, Julian Foad <julianfoad_at_btopenworld.com> wrote:
>> On Tue, 2008-11-25 at 07:27 +0100, Neels J Hofmeyr wrote:
>>> Final scrutiny and merge on tc_url_rev, please.
>>> It's too late for me again.
>> My plan for right now is to fix the test failures on the branch (some
>> more have appeared :-( ) and then reintegrate it
> Could I suggest to keep the branches to "zero test failure" like the
> trunk? That when a failure happens, to stop work and fix it?

But I'm not running tests all the time... I'm wondering how you guys out
there handle the tests. Do you run make check or only selected parts of the
test suite, how often do you run it, how long does it take you to do that
and how do you evaluate which test failures were actually introduced by you?

For me a make check is very time-consuming to pull off. Instead, I run e.g.
only the update_tests and switch_tests when I worked on update, but that's
pretty much it.


> It certainly would make review/test easier when there ate no failures.
> Cheers,
> -g
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe_at_subversion.tigris.org
> For additional commands, e-mail: dev-help_at_subversion.tigris.org

Received on 2008-11-26 05:36:08 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.