test failure in mercurial-3.4

[Matt Mackall]

On Sun, 2015-05-03 at 11:15 +0200, Thomas Klausner wrote:
> Hi!
> 
> With python-2.7.9 on NetBSD-7.99.13/amd64 I have a new test failure in
> the mercurial 3.4 release:

> --- /scratch/devel/py-mercurial/work/mercurial-3.4/tests/test-bundle2-exchange.t
> +++ /scratch/devel/py-mercurial/work/mercurial-3.4/tests/test-bundle2-exchange.t.err
> @@ -707,13 +707,8 @@
>    $ hg -R main push http://localhost:$HGPORT2/ -r e7ec4e813ba6
>       pushing to http://localhost:$HGPORT2/
>          searching for changes
> 	 -  remote: adding changesets
> 	 -  remote: adding manifests
> 	 -  remote: adding file changes
> 	 -  remote: added 1 changesets with 1 changes to 1 files
> 	 -  remote: Fail early!
> 	 -  remote: transaction abort!
> 	 -  remote: Cleaning up the mess...
> 	 -  remote: rollback completed
> 	 -  abort: pretxnchangegroup hook exited with status 1
> 	 -  [255]
> 	 +  no changes found
> 	 +  remote: pre-close-tip:32af7686d403 public book_32af
> 	 +  remote: You shall not pass!
> 	 +  abort: pretxnclose.failpush hook exited with status 1
> 	 +  [255]

We've got a few instabilities in the bundle2 tests, but I haven't seen
this one.

> Should I file a bug report?

Yep.

-- 
Mathematics is the supreme nostalgia of our time.