bzr-svn selftest failures on windows

Bug #460613 reported by Alexander Belchenko
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Bazaar Subversion Plugin
Invalid
Undecided
Unassigned

Bug Description

See attached log of running bzr selftest -s bp.svn on windows with bzr 2.0.1 and bzr-svn trunk revno.3205

Here is console output:

C:\Temp>bzr selftest -s bp.svn > test-svn.log
Unable to remove testing dir edCommitTests.test_commit_joincommit.JoinedCommitTests.test_commit_join
Unable to remove testing dir mmit.TestNativeCommit.test_mwhsts.test_commit.TestNativeCommit.test_mwh
Unable to remove testing dir stPush.test_commit_rename_filests.test_commit.TestPush.test_commit_rename_file
Unable to remove testing dir mit_rename_file_from_directory_0s.test_commit.TestPush.test_commit_rename_file_from_di
Unable to remove testing dir st_commit_rename_remove_parentsts.test_commit.TestPush.test_commit_rename_remove_paren
Unable to remove testing dir t_rename_from_unicode_filenamests.test_commit.TestPush.test_rename_from_unicode_filena
Unable to remove testing dir _fetch_special_becomes_symlink
Unable to remove testing dir shNewBranchTests.test_multiplests.test_push.PushNewBranchTests.test_multiple
Unable to remove testing dir ests.test_multiple_part_existssts.test_push.PushNewBranchTests.test_multiple_part_exis
Unable to remove testing dir Tests.test_push_non_lhs_parentsts.test_push.PushNewBranchTests.test_push_non_lhs_paren
Unable to remove testing dir t_push_replace_existing_branchsts.test_push.PushNewBranchTests.test_push_replace_exist
Unable to remove testing dir TestDPush.test_change_multiplets.test_push.TestDPush.test_change_multiple
Unable to remove testing dir test_push.TestPush.test_changets.test_push.TestPush.test_change
Unable to remove testing dir ush.test_different_branch_pathsts.test_push.TestPush.test_different_branch_path
Unable to remove testing dir WorkingTree.test_commit_nested
Unable to remove testing dir Branch.test_push_create_prefixns.svn.tests.test_blackbox.TestBranch.test_push_create_p
bzr: ERROR: unknown command "fed.py"1 missing] bzrlib.plugins.svn.tests.test_blackbox.TestBranch.test_set_branching
bzr: ERROR: unknown command "fed.py" 1 missing] bzrlib.plugins.svn.tests.test_blackbox.TestBranch.test_set_branchin
Unable to remove testing dir ts.test_push_unnecessary_mergegins.svn.tests.mapping3.RepositoryTests.test_push_unnece
Unable to remove testing dir testbzr-lrmlw6.tmp
[Error 5] : u'C:/tmp/testbzr-lrmlw6.tmp\\ts.test_push_unnecessary_merge\\work\\a\\db\\revs\\0\\1'

Revision history for this message
Alexander Belchenko (bialix) wrote :
Revision history for this message
Jelmer Vernooij (jelmer) wrote : Re: [Bug 460613] Re: bzr-svn selftest failures on windows

Hi,

Thanks for the bug report.

What version of bzr-rebase do you have installed? It seems like the
version of bzr-svn you are using is not compatible with this version of
bzr-rebase (for the purpose of foreign-mapping-upgrade).

Cheers,

Jelmer

--
Jelmer Vernooij <email address hidden> - http://samba.org/~jelmer/
Jabber: <email address hidden>

Revision history for this message
Alexander Belchenko (bialix) wrote :

Jelmer Vernooij пишет:
> What version of bzr-rebase do you have installed? It seems like the
> version of bzr-svn you are using is not compatible with this version of
> bzr-rebase (for the purpose of foreign-mapping-upgrade).

I'm using latest version from trunk.

bzr plugins -v
...
rebase 0.5.4
    Rebase support.
    C:\work\Bazaar\plugins\rebase
...

C:\work\Bazaar\plugins\rebase>bzr pull
Using saved parent location: http://people.samba.org/bzr/jelmer/bzr-rebase/trunk/
No revisions to pull.

C:\work\Bazaar\plugins\rebase>bzr revno
173

Revision history for this message
Jelmer Vernooij (jelmer) wrote :

Can you please run this again with a newer version of bzr-svn ?

Changed in bzr-svn:
status: New → Incomplete
Revision history for this message
Jelmer Vernooij (jelmer) wrote :

If there are still errors, please repoen.

Changed in bzr-svn:
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Bug attachments

Remote bug watches

Bug watches keep track of this bug in other bug trackers.