[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: svn commit: rev 7252 - trunk/tools/cvs2svn

From: Russell Yanofsky <rey4_at_columbia.edu>
Date: 2003-09-30 18:04:10 CEST

maxb@tigris.org wrote:
> Author: maxb
> Date: Tue Sep 30 08:40:13 2003
> New Revision: 7252
>
> Modified:
> trunk/tools/cvs2svn/cvs2svn.py
> trunk/tools/cvs2svn/run-tests.py
> Log:
> Revert revisions 7246 and 7247. These were from a partial committer
> outside their designated area, and caused many testsuite failures.

I don't dispute that I committed outside my area. But I don't see the
testsuite failures. Revision 7247 on linux gives:

$ ./run-tests.py
PASS: run-tests.py 1: cvs2svn with no arguments shows usage
PASS: run-tests.py 2: fail 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
PASS: 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: handle a control char in a log message
XFAIL: run-tests.py 9: handle tags rooted in a redeleted revision
PASS: run-tests.py 10: two commits in quick succession
PASS: run-tests.py 11: prune, but never too much
PASS: run-tests.py 12: file deleted twice, in the root of the repository
PASS: run-tests.py 13: simple trunk commits
PASS: run-tests.py 14: two interleaved trunk commits, different log msgs
XFAIL: run-tests.py 15: simple tags
PASS: run-tests.py 16: simple branch commits
PASS: run-tests.py 17: a commit affecting both trunk and a branch
PASS: run-tests.py 18: branch created from both trunk and another branch
PASS: run-tests.py 19: resyncing should not misorder commit groups

Same revision on windows gives

C:\Download\svn\tools\cvs2svn>python run-tests.py
PASS: run-tests.py 1: cvs2svn with no arguments shows usage
PASS: run-tests.py 2: fail 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: handle a control char in a log message
XFAIL: run-tests.py 9: handle tags rooted in a redeleted revision
PASS: run-tests.py 10: two commits in quick succession
PASS: run-tests.py 11: prune, but never too much
PASS: run-tests.py 12: file deleted twice, in the root of the repository
PASS: run-tests.py 13: simple trunk commits
PASS: run-tests.py 14: two interleaved trunk commits, different log msgs
XFAIL: run-tests.py 15: simple tags
PASS: run-tests.py 16: simple branch commits
PASS: run-tests.py 17: a commit affecting both trunk and a branch
PASS: run-tests.py 18: branch created from both trunk and another branch
PASS: run-tests.py 19: resyncing should not misorder commit groups

- Russ

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Sep 30 18:04:23 2003

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.