[issue484] traceback from debugstate with mtime=-1 under win32
Patrick Mézard
mercurial-bugs at selenic.com
Mon Jan 22 16:15:55 CST 2007
New submission from Patrick Mézard <pmezard at gmail.com>:
Hello,
when formatting file state, time.localtime(-1) raises a ValueError under win32
with python 2.5. mtime==-1 happens after checkouts in a merge context.
test-filebranch triggers the error, and can be simplified here like:
"""
hg init a
cd a
echo 1 > foo
echo 1 > bar
hg commit -Am "base" -d "1000000 0"
cd ..
hg clone a b
echo creating branch a
cd a
echo 2a > foo
echo 2a > bar
hg commit -m "branch a" -d "1000000 0"
echo creating branch b
cd ..
cd b
echo 2b > foo
hg commit -m "branch b" -d "1000000 0"
hg debugstate
echo merging
hg pull ../a
hg merge -v
# Raise here
hg debugstate
"""
A patch detecting mtime==-1 and rewriting the output as "Unknown" is attached.
----------
files: debugstate_neg_mtime
messages: 2716
nosy: pmezard
priority: bug
status: unread
title: traceback from debugstate with mtime=-1 under win32
topic: windows
____________________________________________________
Mercurial issue tracker <mercurial-bugs at selenic.com>
<http://www.selenic.com/mercurial/bts/issue484>
____________________________________________________
-------------- next part --------------
A non-text attachment was scrubbed...
Name: debugstate_neg_mtime
Type: application/octet-stream
Size: 1247 bytes
Desc: not available
Url : http://www.selenic.com/pipermail/mercurial-devel/attachments/20070122/ee5c7923/debugstate_neg_mtime.obj
More information about the Mercurial-devel
mailing list