mercurial-1.3.1 self-test fails on fedora

[Mads Kiilerich]

On 07/24/2009 02:22 PM, Neal Becker wrote:
> + /usr/bin/python run-tests.py
> .............................s....................sssssss.sssssss..s...ssss.ssssssss.............................................s......................s.
> ERROR: test-http output changed
> --- Expected output
> +++ Test output
> @@ -34,11 +34,6 @@
>   1 files, 1 changesets, 1 total revisions
>   adding bar
>   % pull
> -changegroup hook: HG_NODE=cfbd11a1fa315300a080c3de8fe36b0fc5820acf
> HG_SOURCE=pull HG_URL=http://localhost/
>   pulling from http://localhost/
>   searching for changes
> -adding changesets
> -adding manifests
> -adding file changes
> -added 1 changesets with 1 changes to 1 files
> -(run 'hg update' to get a working copy)
> +no changes found
> !.............................................................................................s................................................................................................
>
>    

I don't see that failure on Fedora 11 here. It looks like is caused by 
some kind of unfortunate timing in the test.

I do however see failing inotify tests.

I think the best advice to you is that the Mercurial test suite is 
intended for developers and testers, not for inclusion in automatic 
release builds. As packager you could run the test suite manually on the 
release candidates - that would have more value.

The Mercurial test suite is not unit tests testing small parts of the 
code in artificial situations in 100% reproducible environments. Instead 
it tests the whole Mercurial system in real use cases, and it thus tests 
differently and catches many bugs that unit tests wouldn't have caught - 
including some bugs that isn't there.

/Mads