|
List Info
Thread: Win32 python errors
|
|
| Win32 python errors |
|
2006-06-07 15:48:58 |
Michael,
For previous post: I did _not_ make both changes (sorry
about that).
For this post I did. I ran the script twice (without having
to delete
the statistics file for the second time).
It seems to believe it was successful (output files are
available but
quite large).
The run-tests.py script failed on almost all tests. Output
below.
Question:
Is there a standard cvs repository used for testing? The
one I have is
rather large and mostly degenerate (all trunk, few branches,
no 'tricky'
stuff). It also seems to take quite a while.
I suppose that the first place to start is in test 3...?
<SNIP>
Starting Subversion r5162 / 5162
Done.
cvs2svn Statistics:
------------------
Total CVS Files: 4259
Total CVS Revisions: 17561
Total Unique Tags: 29
Total Unique Branches: 14
CVS Repos Size in KB: 642402
Total SVN Commits: 5162
First Revision Date: Sun Jul 13 20:37:25 2003
Last Revision Date: Mon May 22 16:26:49 2006
------------------
Timings:
------------------
pass 1: 222 seconds
pass 2: 3 seconds
pass 3: 2 seconds
pass 4: 4 seconds
pass 5: 5 seconds
pass 6: 0 seconds
pass 7: 0 seconds
pass 8: 3777 seconds
total: 4016 seconds
C:\CVS\cvs2svn-1.3.0>dir
Volume in drive C is Local Disk
Volume Serial Number is 5CF5-EE19
Directory of C:\CVS\cvs2svn-1.3.0
06/07/2006 10:54 AM <DIR> .
06/07/2006 10:54 AM <DIR> ..
08/18/2005 09:52 PM 1,847 BUGS
08/18/2005 10:07 PM 1,654 CHANGES
06/07/2006 09:33 AM 592,177 change_both.txt
06/07/2006 10:54 AM 592,179 change_both_2nd.txt
08/18/2005 09:52 PM 926 COMMITTERS
08/18/2005 09:52 PM 2,725 COPYING
06/07/2006 07:49 AM 198,183 cvs2svn
08/18/2005 10:10 PM 5,635 cvs2svn.1
06/05/2006 03:03 PM <DIR>
cvs2svn_rcsparse
06/06/2006 09:09 AM 198,182 cvs2svn~
08/18/2005 09:52 PM 22,265 design-notes.txt
08/18/2005 10:09 PM 1,338 dist.sh
08/18/2005 09:52 PM 991 dump-db.py
08/18/2005 09:52 PM 652 HACKING
08/18/2005 09:52 PM 457 Makefile
08/18/2005 10:10 PM 262 PKG-INFO
08/18/2005 09:52 PM 2,957 profile-repos.py
08/18/2005 09:52 PM 83 README
06/06/2006 09:06 AM 845 run-test.b4.txt
08/18/2005 09:52 PM 69,813 run-tests.py
08/18/2005 09:52 PM 768 setup.py
08/18/2005 09:52 PM 2,663 show-db.py
11/11/1999 12:00 AM 38,400 sort.exe
06/06/2006 09:03 AM <DIR> svntest
06/05/2006 01:53 PM <DIR> test-data
06/07/2006 08:13 AM <DIR> tmp
08/18/2005 09:52 PM 12,823 verify-cvs2svn
06/05/2006 01:53 PM <DIR> www
23 File(s) 1,747,825 bytes
7 Dir(s) 27,541,917,696 bytes free
C:\CVS\cvs2svn-1.3.0>python run-tests.py
PASS: run-tests.py 1: cvs2svn with no arguments shows usage
SKIP: run-tests.py 2: detection of the executable flag
FAIL: run-tests.py 3: conversion of filename with a space
FAIL: run-tests.py 4: two commits in quick succession
FAIL: run-tests.py 5: prune, but never too much
FAIL: run-tests.py 6: two interleaved trunk commits,
different log msgs
FAIL: run-tests.py 7: simple trunk commits
FAIL: run-tests.py 8: simple tags and branches with no
commits
FAIL: run-tests.py 9: simple branch commits
FAIL: run-tests.py 10: mixed-time tag
FAIL: run-tests.py 11: mixed-time branch, and a file added
to the branch
FAIL: run-tests.py 12: a commit affecting both trunk and a
branch
FAIL: run-tests.py 13: branch some trunk files, and later
branch the rest
FAIL: run-tests.py 14: conversion of invalid symbolic names
UNEXPECTED EXCEPTION:
Traceback (most recent call last):
File
"C:\CVS\cvs2svn-1.3.0\svntest\testcase.py",
line 105, in run
rc = apply(self.pred.func, args)
File "run-tests.py", line 828, in
overlapping_branch
if not (logs[rev].changed_paths.get('/branches/vendorA
(from /trunk:3)')
KeyError: 4
FAIL: run-tests.py 15: ignore a file with a branch with two
names
FAIL: run-tests.py 16: convert a branch file rooted in a
'dead' revision
FAIL: run-tests.py 17: handle a control char in a log
message
FAIL: run-tests.py 18: handle tags rooted in a redeleted
revision
FAIL: run-tests.py 19: ensure that trunk doesn't get
pruned
FAIL: run-tests.py 20: file deleted twice, in the root of
the repository
FAIL: run-tests.py 21: branch created from both trunk and
another branch
FAIL: run-tests.py 22: resyncing should not misorder commit
groups
FAIL: run-tests.py 23: allow tags with mixed trunk and
branch sources
FAIL: run-tests.py 24: never use the rev-in-progress as a
copy source
FAIL: run-tests.py 25: do use the last completed rev as a
copy source
FAIL: run-tests.py 26: correctly handle deletion as initial
branch action
SKIP: run-tests.py 27: non ascii files converted
incorrectly
FAIL: run-tests.py 28: avoid spurious changes for initial
revs
FAIL: run-tests.py 29: handle default branches correctly
FAIL: run-tests.py 30: compose a tag from three sources
FAIL: run-tests.py 31: reserve a svn revnum for a fill only
when required
FAIL: run-tests.py 32: make sure that filling prunes paths
correctly
FAIL: run-tests.py 33: don't break when the trunk is empty
FAIL: run-tests.py 34: ensure that we don't create any
spurious commits
FAIL: run-tests.py 35: verify correct revs are copied to
default branches
FAIL: run-tests.py 36: run each pass individually
FAIL: run-tests.py 37: reveal a big bug in our resync
algorithm
FAIL: run-tests.py 38: reveal a bug in our default branch
detection code
PASS: run-tests.py 39: die if a file exists in and out of
the attic
FAIL: run-tests.py 40: reveal a big bug in our
SymbolicNameFillingGuide
FAIL: run-tests.py 41: test eol settings and mime types
together
FAIL: run-tests.py 42: test setting of svn:keywords
property among others
FAIL: run-tests.py 43: test setting of svn:ignore property
FAIL: run-tests.py 44: test that CVS can still do what RCS
can't
FAIL: run-tests.py 45: test that we can handle weird
symbolic names
FAIL: run-tests.py 46: reveal a bug that reorders file
revisions
FAIL: run-tests.py 47: test that exclude really excludes
everything
FAIL: run-tests.py 48: add trunk file that was deleted on
vendor branch
FAIL: run-tests.py 49: ensure pass2 doesn't pull rev too
far forward
FAIL: run-tests.py 50: only LFs for svn:eol-style=native
files
FAIL: run-tests.py 51: reveal a bug that created a branch
twice
FAIL: run-tests.py 52: ensure pass2 doesn't push rev too
far backward
FAIL: run-tests.py 53: reveal a bug that added a branch
file twice
FAIL: run-tests.py 54: reveal a bug that copies a branch
file wrongly
C:\CVS\cvs2svn-1.3.0>
--
Rick Zemer
Exacq Technologies
rzemer exacq.com
317.845.5710
------------------------------------------------------------
---------
To unsubscribe, e-mail: users-unsubscribecvs2svn.tigris.org
For additional commands, e-mail: users-helpcvs2svn.tigris.org
|
|
| Win32 python errors |
|
2006-06-07 19:27:28 |
Rick Zemer wrote:
> For previous post: I did _not_ make both changes (sorry
about that).
> For this post I did. I ran the script twice (without
having to delete
> the statistics file for the second time).
> It seems to believe it was successful (output files are
available but
> quite large).
>
> The run-tests.py script failed on almost all tests.
Output below.
> Question:
> Is there a standard cvs repository used for testing?
The one I have is
> rather large and mostly degenerate (all trunk, few
branches, no 'tricky'
> stuff). It also seems to take quite a while.
There are a whole bunch of small but diabolical test
repositories along
with the cvs2svn source code (for example if you check it
out from its
subversion repository) under the test-data directory. The
run-tests.py
script processes these test repositories for its tests.
> I suppose that the first place to start is in test
3...?
Yes. But it would make more sense to work on trunk instead
of the 1.3.x
branch, which is rather old code. Could you check out the
current
cvs2svn trunk and do further testing there? The URL,
username and
password are listed on the main cvs2svn project page.
Also please make sure that you have RCS installed. That
package
supplies the co.exe program which is needed by cvs2svn.
Then indeed the next things is to start analyzing the
failing tests one
by one using "python run-test.py -v
TEST_NUMBER".
Michael
------------------------------------------------------------
---------
To unsubscribe, e-mail: users-unsubscribecvs2svn.tigris.org
For additional commands, e-mail: users-helpcvs2svn.tigris.org
|
|
| Win32 python errors |
|
2006-06-07 20:13:14 |
After installing RCS, all the tests (except 43, 44) passed.
Synopsis: making the changes to cvs2svn requested by MH, and
installing
RCS. All appears well.
I suppose this means, that I am done...
If, however, my help (in testing, debugging, or development)
is still of
value, please let me know.
Thanks for your help -- it is greatly appreciated. And
thank you for
making our transition to Subversion so (relatively) simple.
Michael Haggerty wrote:
> Rick Zemer wrote:
>
>> For previous post: I did _not_ make both changes
(sorry about that).
>> For this post I did. I ran the script twice
(without having to delete
>> the statistics file for the second time).
>> It seems to believe it was successful (output files
are available but
>> quite large).
>>
>> The run-tests.py script failed on almost all
tests. Output below.
>> Question:
>> Is there a standard cvs repository used for
testing? The one I have is
>> rather large and mostly degenerate (all trunk, few
branches, no 'tricky'
>> stuff). It also seems to take quite a while.
>>
>
> There are a whole bunch of small but diabolical test
repositories along
> with the cvs2svn source code (for example if you check
it out from its
> subversion repository) under the test-data directory.
The run-tests.py
> script processes these test repositories for its tests.
>
>
>> I suppose that the first place to start is in test
3...?
>>
>
> Yes. But it would make more sense to work on trunk
instead of the 1.3.x
> branch, which is rather old code. Could you check out
the current
> cvs2svn trunk and do further testing there? The URL,
username and
> password are listed on the main cvs2svn project page.
>
> Also please make sure that you have RCS installed.
That package
> supplies the co.exe program which is needed by cvs2svn.
>
> Then indeed the next things is to start analyzing the
failing tests one
> by one using "python run-test.py -v
TEST_NUMBER".
>
> Michael
>
>
>
--
Rick Zemer
Exacq Technologies
rzemerexacq.com
317.845.5710
------------------------------------------------------------
---------
To unsubscribe, e-mail: users-unsubscribecvs2svn.tigris.org
For additional commands, e-mail: users-helpcvs2svn.tigris.org
|
|
| Win32 python errors |
|
2006-06-07 20:36:35 |
Rick Zemer wrote:
> After installing RCS, all the tests (except 43, 44)
passed.
What happened with 43 and 44? What was the "-v"
output?
Michael
------------------------------------------------------------
---------
To unsubscribe, e-mail: users-unsubscribecvs2svn.tigris.org
For additional commands, e-mail: users-helpcvs2svn.tigris.org
|
|
| Win32 python errors |
|
2006-06-07 20:55:14 |
Test 43 generates this:
CMD: python.exe
"C:\CVS\cvs2svn-1.3.0\cvs2svn"
"--bdb-txn-nosync" "-s"
"cvsignore-svnrepos"
"C:\CVS\cvs2svn-1.3.0\test-data\cvsignore-cvsrepos
"
<TIME = 2.875000>
CMD: svn "co"
"file:///C:/CVS/cvs2svn-1.3.0/tmp/cvsignore-svnrepos&
quot;
"cvsignore-wc" <TIME = 0.953000>
CMD: svn "log" "-v"
"file:///C:/CVS/cvs2svn-1.3.0/tmp/cvsignore-svnrepos&
quot; <TIME = 0.094000>
CMD: svn "proplist"
"tmp\cvsignore-wc" "--verbose"
"--config-dir"
"C:\CVS\cvs2svn-1.3.0\svn-test-work\local_tmp\con
fig" <TIME = 0.047000>
CMD: svn "proplist"
"tmp\cvsignore-wc\branches"
"--verbose"
"--config-dir"
"C:\CVS\cvs2svn-1.3.0\svn-test-work\local_tmp\con
fig"
<TIME = 0.063000>
CMD: svn "proplist"
"tmp\cvsignore-wc\tags"
"--verbose" "--config-dir"
"C:\CVS\cvs2svn-1.3.0\svn-test-work\local_tmp\con
fig" <TIME = 0.047000>
CMD: svn "proplist"
"tmp\cvsignore-wc\trunk"
"--verbose" "--config-dir"
"C:\CVS\cvs2svn-1.3.0\svn-test-work\local_tmp\con
fig" <TIME = 0.046000>
CMD: svn "proplist"
"tmp\cvsignore-wc\trunk\proj"
"--verbose"
"--config-dir"
"C:\CVS\cvs2svn-1.3.0\svn-test-work\local_tmp\con
fig"
<TIME = 0.063000>
CMD: svn "proplist"
"tmp\cvsignore-wc\trunk\proj\.cvsignore"
"--verbose"
"--config-dir"
"C:\CVS\cvs2svn-1.3.0\svn-test-work\local_tmp\con
fig"
<TIME = 0.047000>
CMD: svn "proplist"
"tmp\cvsignore-wc\trunk\proj\file.txt"
"--verbose"
"--config-dir"
"C:\CVS\cvs2svn-1.3.0\svn-test-work\local_tmp\con
fig"
<TIME = 0.062000>
CMD: svn "proplist"
"tmp\cvsignore-wc\trunk\proj\subdir"
"--verbose"
"--config-dir"
"C:\CVS\cvs2svn-1.3.0\svn-test-work\local_tmp\con
fig"
<TIME = 0.047000>
CMD: svn "proplist"
"tmp\cvsignore-wc\trunk\proj\subdir\.cvsignore&q
uot;
"--verbose" "--config-dir"
"C:\CVS\cvs2svn-1.3.0\svn-test-work\local_tmp\con
fig" <TIME = 0.047000>
FAIL: run-tests.py 43: test setting of svn:ignore property
Test 44 generates this:
CMD: python.exe
"C:\CVS\cvs2svn-1.3.0\cvs2svn"
"--use-cvs"
"--bdb-txn-nosync" "-s"
"requires-cvs--use-cvs-svnrepos"
"C:\CVS\cvs2svn-1.3.0\test-data\requires-cvs-cvsre
pos" <TIME = 8.266000>
C:\Python23\python.exe said:
ERROR: error executing CVS: status None, error output:
FAIL: run-tests.py 44: test that CVS can still do what RCS
can't
Michael Haggerty wrote:
> Rick Zemer wrote:
>
>> After installing RCS, all the tests (except 43, 44)
passed.
>>
>
> What happened with 43 and 44? What was the
"-v" output?
>
> Michael
>
>
>
--
Rick Zemer
Exacq Technologies
rzemerexacq.com
317.845.5710
------------------------------------------------------------
---------
To unsubscribe, e-mail: users-unsubscribecvs2svn.tigris.org
For additional commands, e-mail: users-helpcvs2svn.tigris.org
|
|
[1-5]
|
|