[csw-buildfarm] Fwd: Mercurial 2.0 call for testing
rupert at opencsw.org
Mon Oct 17 07:28:30 CEST 2011
hi, as i understood cvs-upload automatically updates unstable9s,
unstable10s. end of last week i compiled svn-1.7.0 - and it is not yet
---------- Forwarded message ----------
From: Mads Kiilerich <mads at kiilerich.com>
Date: Mon, Oct 17, 2011 at 00:19
Subject: Re: Mercurial 2.0 call for testing
To: "rupert.thurner" <rupert.thurner at gmail.com>
Cc: mercurial at selenic.com
rupert.thurner wrote, On 10/16/2011 09:34 PM:
> for solaris the folloing unit tests fail:
> Failed test-highlight.t: output changed, see http://pastebin.com/RgQbkaka
That seems to be an internal problem in the pygments installation:
+ File "/opt/csw/lib/python/site-packages/pkg_resources.py", line
565, in resolve
+ raise DistributionNotFound(req) # XXX put more info here
+ DistributionNotFound: MarkupSafe>=0.9.2
It works fine on current9x.
> Failed test-progress.t: output changed, see http://pastebin.com/4K8NaEHH
Strange. Random failures on unstable9x, apparently related to the
shell and pipings and redirects and when the pipes are closed. No
problems on current9x and current10x.
> Failed test-convert-svn-sink.t: output changed, see http://pastebin.com/jAH3Ewgw
"svn exited with status 256" - and it gives no indication what the
problem could be. That must be some kind of svn issue.
I guess you are using svn 1.7.0-rc3. Can you try to update to the real
1.7.0? It is very likely that they have made non backward compatible
changes and that Mercurial doesn't support it (yet) (at least not in
the test suite).
> Failed test-subrepo-svn.t: output changed and returned error code 1,
> see http://pastebin.com/Jmwd9TXQ
Yes, I had a workaround for that in my queue - it is in crew now. Yet
another solaris bug.
More information about the buildfarm