cmpilato@collab.net wrote:
> "Russell Yanofsky" <rey4@columbia.edu> writes:
>
>> Log Message:
>>
>> Changes to cvs2svn.py and its regression testing script so they will
>> work on Windows.
>
> [...]
>
>> (pass3): Changed to sort the file listing in memory instead of with
>> the "sort" command on Windows. Original behavior is preserved on
>> other platforms.
>
> I'm confused. Windows has a 'sort' program that supports path input
> and redirected I/O. Why not use it? Does it behave differently than
> it should?
The windows sort program does seem to work some times, but it fails at other
times. Here are the test results when the sort program is used:
M:\russ\source\svn\tools\cvs2svn>python run-tests.py
PASS: run-tests.py 1: cvs2svn with no arguments shows usage
PASS: run-tests.py 2: fail early on encountering an invalid symbolic name
PASS: run-tests.py 3: fail early on encountering a branch with two names
FAIL: run-tests.py 4: convert as much as can, despite a corrupt ,v file
FAIL: run-tests.py 5: convert a branch file rooted in a 'dead' revision
FAIL: run-tests.py 6: detection of the executable flag
FAIL: run-tests.py 7: conversion of filename with a space
FAIL: run-tests.py 8: two commits in quick succession
FAIL: run-tests.py 9: prune, but never too much
FAIL: run-tests.py 10: file deleted twice, in the root of the repository
FAIL: run-tests.py 11: simple trunk commits
FAIL: run-tests.py 12: two interleaved trunk commits, with different log msgs
XFAIL: run-tests.py 13: simple tags
XFAIL: run-tests.py 14: simple branch commits
XFAIL: run-tests.py 15: a commit affecting both trunk and a branch
FAIL: run-tests.py 16: branch created from both trunk and from another branch
FAIL: run-tests.py 17: resyncing should not put commit groups in the wrong
order
And here are the results when in memory sorting is used:
M:\russ\source\svn\tools\cvs2svn>python run-tests.py
PASS: run-tests.py 1: cvs2svn with no arguments shows usage
PASS: run-tests.py 2: fail early on encountering an invalid symbolic name
PASS: run-tests.py 3: fail early on encountering a branch with two names
PASS: run-tests.py 4: convert as much as can, despite a corrupt ,v file
PASS: run-tests.py 5: convert a branch file rooted in a 'dead' revision
FAIL: run-tests.py 6: detection of the executable flag
PASS: run-tests.py 7: conversion of filename with a space
PASS: run-tests.py 8: two commits in quick succession
PASS: run-tests.py 9: prune, but never too much
PASS: run-tests.py 10: file deleted twice, in the root of the repository
PASS: run-tests.py 11: simple trunk commits
PASS: run-tests.py 12: two interleaved trunk commits, with different log msgs
XFAIL: run-tests.py 13: simple tags
XFAIL: run-tests.py 14: simple branch commits
XFAIL: run-tests.py 15: a commit affecting both trunk and a branch
PASS: run-tests.py 16: branch created from both trunk and from another branch
PASS: run-tests.py 17: resyncing should not put commit groups in the wrong
order
I don't remember what causes this, but I'll look into it.
- Russ
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Jul 26 01:35:09 2003