Assertion failure after renaming and deleting

[John Arbash Meinel]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Weeble wrote:
> I reported what I think was the same problem earlier today, but I used
> a different email address and it got postponed for moderation. I have
> attempted to reproduce the bug with a minimal number of steps. Working
> in Windows, the following batch file exhibits the problem:

I believe this is a known bug which has been fixed and will be in 0.17rc1 next
week.

Are you able to try with the latest development version? Or can you try it
again after 0.17rc1 is available?

Also, you didn't provide what version of bzr you are running. This bug may have
even been fixed in 0.16. (It looks like you are running 0.15 to me, and this
bug was fixed, but it may be a different bug which we have fixed for 0.17).

I realize that since you are running on windows, you are probably running the
standalone installer, rather than the python installer, so it is a bit
difficult to get you running a development snapshot. But if you are willing to
try, we should be able to help you on IRC (channel #bzr or irc.freenode.net).


Can you at least include the version of bzr you are running? (bzr --version is
sufficient). And if you are running 0.15, there is an 0.16 which is already
available. And 0.17rc1 will be out on Tuesday (though it may take a day to
produce a win32 installer).

I'm going to try to reproduce this with different bzr versions to make sure,
and I'll post a followup.

John
=:->



> 
> REM ===== START OF TEST.BAT =====
> setlocal
> set DIR1=%1
> set DIR2=%2
> set FILE1=%3
> set FILE2=%4
> 
> mkdir %DIR1%
> echo Blah blah blah > %DIR1%\%FILE1%
> 
> bzr init
> bzr add %DIR1%
> bzr commit -m "Initial setup"
> 
> cd %DIR1%
> bzr rename %FILE1% %FILE2%
> del %FILE2%
> cd ..
> bzr rename %DIR1% %DIR2%
> 
> bzr status
> 
> bzr commit -m "This sometimes causes an assertion failure"
> REM ===== END OF TEST.BAT =====
> 
> When I run it (in an otherwise empty directory) with:
> 
> TEST.BAT spam eggs foo bar
> 
> It produces an assertion failure.[1] However, when I run it with:
> 
> TEST.BAT foo spam bar.txt baz.txt
> 
> ...it finishes with no errors. I'm hoping that's useful information to
> figure out what's going on. Apologies if this is already reported.
> Also note that I don't know if I'm trying to do something that's not
> allowed, but I think that even if I am I should get a useful error
> somewhere along the line, and not a nasty assertion failure.
> 
> Regards,
>    Weeble.
> 
> [1] The assertion failure:
> 
> C:\baztest>bzr commit -m "This sometimes causes an assertion failure"
> missing eggs/bar
> renamed spam => eggs
> deleted spam/foo
> bzr: ERROR: exceptions.AssertionError: file
> foo-20070608134934-jzv36hb2z6jlvee0-2 is absent in row (('spam',
> 'foo', 'foo-20070608134934-jzv36hb2z6jlvee0-2'), [('a', '', 0, False,
> ''), ('f', 'c5f067b4cfe235ef53e161ad329e15f8c9ba7b0c', 17, False,
> 'andrew.wilson at xxxxxxxxxxxxxx.com-20070608134934-ljt9yjqf9a7k0t4p')])
> but also present at 'eggs/bar'
> 
> Traceback (most recent call last):
>  File "bzrlib\commands.pyc", line 718, in run_bzr_catch_errors
>  File "bzrlib\commands.pyc", line 679, in run_bzr
>  File "bzrlib\commands.pyc", line 375, in run_argv_aliases
>  File "bzrlib\builtins.pyc", line 2210, in run
>  File "bzrlib\decorators.pyc", line 165, in write_locked
>  File "bzrlib\workingtree_4.pyc", line 245, in commit
>  File "bzrlib\decorators.pyc", line 165, in write_locked
>  File "bzrlib\mutabletree.pyc", line 195, in commit
>  File "bzrlib\commit.pyc", line 347, in commit
>  File "bzrlib\mutabletree.pyc", line 38, in tree_write_locked
>  File "bzrlib\workingtree_4.pyc", line 1069, in set_parent_trees
>  File "bzrlib\dirstate.pyc", line 2269, in _validate
> AssertionError: file foo-20070608134934-jzv36hb2z6jlvee0-2 is absent
> in row (('spam', 'foo', 'foo-20070608134934-jzv36hb2z6jlvee0-2'),
> [('a', '', 0, False, ''), ('f',
> 'c5f067b4cfe235ef53e161ad329e15f8c9ba7b0c', 17, False,
> 'andrew.wilson at xxxxxxxxxxxxxx.com-20070608134934-ljt9yjqf9a7k0t4p')])
> but also present at 'eggs/bar'
> 
> 

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFGaWMTJdeBCYSNAAMRAoXfAJ918qP0OdbuGlrKP8bXe0RgTruY/ACgx1c3
LAqBp/OKzShlYN+Rwk2vA3c=
=VBNd
-----END PGP SIGNATURE-----