Continuious Integration platform for Mercurial

[Martin Geisler]

Bill Barry <after.fallout at gmail.com> writes:

> Martin Geisler wrote:
>> Pierre-Yves David <pierre-yves.david at logilab.fr> writes:
>>
>>   
>>> As I've already talked about on IRC, I have been experimenting with a
>>> continuous integration plateform at http://apycot.hg-scm.org/ . A
>>> production setup now runs several variants of the tests-suite for all
>>> official repo and checks code style and documentation. Notification by
>>> email or RSS is available.
>>>
>>> I hope you'll find it useful, have fun!
>>>     
>>
>> It looks great! Thanks for the time you have put into this, I'm sure
>> this will be useful for us. It's already nice to have the code tested
>> regularly on Python 2.4 since we should keep compatible with that
>> release.
>>
>>   
>
> is the failure on crew/standard/2.4 normal?
>
> http://apycot.hg-scm.org/testexecution/91397?tab=hgtest
>
> How would that even happen? Something runs in different order when
> executing standard vs pure? Or is the test turned off in pure?

No... it is not normal for the tests to fail -- they all pass here,
including test-clone-pull-corruption. It passes both with and without
the --pure flag to run-tests.py. That is with Python 2.5.

It also passes with --pure on Python 2.4. I cannot run it without --pure
since I don't have a python2.4-dev package installled to compile the C
extensions (and I cannot find such a package?).

-- 
Martin Geisler

Fast and powerful revision control: http://mercurial.selenic.com/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: not available
URL: <http://selenic.com/pipermail/mercurial-devel/attachments/20100312/505674a7/attachment.pgp>