Running tests on windows

[Brendan Cully]

On Thursday, 22 March 2012 at 09:20, Matt Mackall wrote:
> And on Mac, there aren't really any excuses. Mercurial installs are
> "hackable" out of the box, the test suite runs, and there's a standard,
> free compiler. There should be enough Mac developers out there that I
> never have to lift a finger to fix Mac bugs and yet we manage to make
> releases like 2.1.1 where no one notices it doesn't compile until after
> it ships.

Ideally yes. On the other hand, there is a buildbot and you do have an
OS X shell, so it wouldn't have taken much more than a lifted finger
to prevent that one. That build-breaking patch was only applied a few
days before release.

Speaking of mac bugs identified by the buildbot,

hg bisect -c "./run-tests.py test-casefolding.t test-casecollision-merge.t"

says

The first bad revision is:
changeset:   16093:7e30f5f2285f
user:        Matt Mackall <mpm at selenic.com>
date:        Thu Feb 09 16:50:19 2012 -0600
summary:     merge: refactor unknown file conflict checking