[PATCH 1 of 1 STABLE V2] merge: increase safety of parallel updating/removing on icasefs

Idan Kamara idankk86 at gmail.com
Fri May 3 03:20:19 CDT 2013

On Tue, Apr 30, 2013 at 10:05 PM, Bryan O'Sullivan <bos at serpentine.com>wrote:

> On Tue, Apr 30, 2013 at 2:43 AM, Mads Kiilerich <mads at kiilerich.com>wrote:
>> The tricky part is to do it in a way where we are sure to exercise all
>> the worst possible partitioning and scheduling ... and in a reliable way
>> and without doubling the time it takes to run the test suite.
> Probably the right way to do this is to set up some config that allows us
> to force parallel updates to be used on platforms where it exists, and then
> to always run the test suite with this flag set (unless specifically
> directed not to).

There's probably enough logic to justify unit tests as well.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://selenic.com/pipermail/mercurial-devel/attachments/20130503/940f9c95/attachment.html>

More information about the Mercurial-devel mailing list