[csw-buildfarm] [csw-maintainers] what is different on buildfarm? mercurial tests take long - or fail

[rupert THURNER]

i tested now hg-1.5 ... and i am wondering why we are back to "stall" on
build8s with

rupert at build8s
:~/mgar/pkg/mercurial/trunk/work/solaris8-sparc/build-isa-sparcv8/mercurial-1.5/tests
$ time python ./run-tests.py test-push-http

did python change back?

rupert.


On Sun, Feb 14, 2010 at 00:05, Mads Kiilerich <mads at kiilerich.com> wrote:

> rupert THURNER wrote, On 02/13/2010 08:00 PM:
>
>
>>
>> On Thu, Feb 11, 2010 at 09:38, Dagobert Michelsen <dam at opencsw.org<mailto:
>> dam at opencsw.org>> wrote:
>>
>>    Hi Mads,
>>
>>    Am 11.02.2010 um 04:03 schrieb Mads Kiilerich:
>>
>>        My conclusion is that the patch is a huge improvement, and as
>>        far as I know there are no problems left. Python.org should
>>        apply the patch in next release, and you should consider to
>>        patch your Python package.
>>
>>
>>    Thanks for testing, I asked Maciej to respin a patched Python,
>>    commented
>>    on the bug and soon we will have a fully-functional Mercurial :-)
>>
>>
>> just for the record - did this really impact mercurial as well, or "only"
>> the test cases?
>>
>
> I don't think it affected Mercurial itself, but it affected some usecases
> for Mercurial.
>
> IIRC it was related to forking. Core Mercurial hardly forks, but it happens
> when for example external hooks are used.
>
> /Mads
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opencsw.org/pipermail/buildfarm/attachments/20100307/116b28d0/attachment.html>