Windows test suite state

[Paul Moore]

On 05/06/2008, Patrick Mézard <pmezard at gmail.com> wrote:
> Paul Moore a écrit :
> > Basically, can I assume that this output qualifies as "the test suite
> > passed" on Windows?
>
> No.
>
> I have updated pysh to rewrite the output of a couple of mercurial commands to
> ease testing. Maybe not the correct solution but it makes everything easier for
> Windows developers, and it can be reverted quickly. The w32-crew patch queue
> was also updated against the new pysh, with the following output:
>
> Skipped test-archive-symlinks: missing feature: symbolic links
> Skipped test-changelog-exec: missing feature: executable bit
> Skipped test-convert-baz: missing feature: GNU Arch baz client
> Skipped test-convert-tla: missing feature: GNU Arch tla client
> Skipped test-execute-bit: missing feature: executable bit
> Skipped test-hgwebdirsym: missing feature: symbolic links
> Skipped test-highlight: missing feature: Pygments source highlighting library
> Skipped test-hup: unknown feature: failure
> Skipped test-inherit-mode: missing feature: unix-style permissions
> Skipped test-issue352: missing feature: end-of-lines in paths
> Skipped test-mq-qclone-http: unknown feature: failure
> Skipped test-mq-symlinks: missing feature: symbolic links
> Skipped test-revert-flags: missing feature: executable bit
> Skipped test-symlink-basic: missing feature: symbolic links
> Skipped test-symlink-root: missing feature: symbolic links
> Skipped test-symlinks: missing feature: symbolic links
> Failed test-convert-git: output changed
> Failed test-convert-hg-source: output changed
> Failed test-convert-svn-sink: output changed
> Failed test-flags: output changed
> Failed test-git-export: output changed
> Failed test-hgwebdir: output changed
> Failed test-imerge: output changed
> Failed test-lock-badness: output changed
> Failed test-merge-types: output changed and returned error code 1
> Failed test-mq: output changed
> Failed test-permissions: output changed
> Failed test-pull-permission: output changed
> # Ran 258 tests, 16 skipped, 12 failed.

OK, that's useful to know. I'll pick up the latest version and
investigate the remaining discrepancies.

> You can find the log of test executions in the "test.log" file of the patch queue. I
> use it to decide whether current version works at least as well as the previous
> one, by diffing these traces (generated by "$ python run-tests.py >test.log
> 2>&1").

Excellent. That's useful to know for the future.

> Finally, I do not have enough time to maintain w32-crew-stable these days.

No problem, I always work on crew anyway. Once I get the case folding
patches finished, I plan on looking at the test suite to see if
there's anything useful that can be done to make it easier to use on
Windows (although it's pretty good now, thanks to your efforts). If
you'd like a hand maintaining the patch series, let me know. If
nothing else, I can probably do occasional rebases of the series, to
free up some of your time.

> Please tell me if you have any problems with the new pysh and new patch queue.

I'll give it a go tonight. And thanks again.

Paul.

PS I had one strange result today. I'll see if it's still there with
the new pysh etc, but I mention it here in case it's something
obvious. I'm getting spurious "added a/b" messages from the test
suite. For example, in test-hgignore the line

    hg add dir/a.o

is returning

    added dir\a.o

where the expected output is empty.

But if I run the same command from the command line, I get no output,
as expected. It's not precisely the same, as for example, I build
hg.exe using py2exe rather than using a temporary install, but before
I start hunting for subtle stuff like that, can I check that there's
nothing special about how the test suite runs Mercurial that might
affect this?