zooko@tahoe-lafs:/data1/homezooko/bench$ darcs-benchmark run --converge
darcs-2.2.0 darcs-2.3.1 darcs-2.4.4 darcs
darcs-benchmark: user error (Pattern match failure in do expression at
source/Benchmark.hs:178:7-21)
zooko@tahoe-lafs:/data1/homezooko/bench$ darcs-benchmark run darcs-2.2.0
darcs-2.3.1 darcs-2.4.4 darcs
darcs-benchmark: user error (Pattern match failure in do expression at
source/Benchmark.hs:178:7-21)

On Fri, Nov 19, 2010 at 07:38:35 +0000, Zooko wrote:
> zooko@tahoe-lafs:/data1/homezooko/bench$ darcs-benchmark run --converge
> darcs-2.2.0 darcs-2.3.1 darcs-2.4.4 darcs
> darcs-benchmark: user error (Pattern match failure in do expression at
> source/Benchmark.hs:178:7-21)
> zooko@tahoe-lafs:/data1/homezooko/bench$ darcs-benchmark run darcs-2.2.0
> darcs-2.3.1 darcs-2.4.4 darcs
> darcs-benchmark: user error (Pattern match failure in do expression at
> source/Benchmark.hs:178:7-21)

Yuck. That's fixed in darcs-benchmark HEAD.

Perhaps we need to make another release...

-- 
Eric Kow <http://www.nltg.brighton.ac.uk/home/Eric.Kow>
For a faster response, try +44 (0)1273 64 2905 or
xmpp:kowey@jabber.fr (Jabber or Google Talk only)

On Mon, Nov 22, 2010 at 12:02:39 +0000, Eric Kow wrote:
> Yuck. That's fixed in darcs-benchmark HEAD.
> 
> Perhaps we need to make another release...

Curse of distributed version control: I forgot to push the patch.
This should be fixed now.

I tried to come up with an automated test for this, involving fake
darcs binaries that spat out various contexts, but I was blocked
by a bunch of intervening stuff [1], and gave up after a couple of
hours of yak-shaving. Sorry! (I do want us to take testing more
seriously, but this is the sort of stuff that happens during the
transition)

[1] Latest progress:
    http://code.haskell.org/darcs/darcs-benchmark/reports/bugs/f45350d5-ea4b-492f-818d-a51124dd0e6f/
-- 
Eric Kow <http://www.nltg.brighton.ac.uk/home/Eric.Kow>
For a faster response, try +44 (0)1273 64 2905 or
xmpp:kowey@jabber.fr (Jabber or Google Talk only)

Why is this unknown? I am changing to resolved, based on msg13209 and 
msg13281. Please take action if this was wrong.