New submission from Mark Stosberg <[EMAIL PROTECTED]>:
To reproduce:
darcs init --hashed --repodir=u2
cd darcs-unstable-repo
time -p darcs push -a --no-set ../u2
Resolving conflicts 5/27
Apply failed!
real 862.99
user 731.10
sys 3.98
###
Darcs takes a very long time and then results in "apply failed". Another minor
bug was expected in the process: The count of conflicts being resolved jumped
around, rather than only increasing. The total count of conflicts to resolve
went up to 600 at one point, and then back down to 27. I would have expected
that the total would only increase.
Perhaps this issue is considered "resolved in unstable" because it wouldn't
happen on projects starting from scratch with Darcs 2, even though it happens
this repo which created earlier.
I was somewhat surprised that pushing to an empty repo didn't approach the
efficiency of a "darcs put".
Mark
----------
messages: 3310
nosy: beschmi, droundy, kowey, markstos, tommy
priority: urgent
status: chatting
title: darcs-unstable (hashed) repo fails to push to empty repo
topic: Darcs2, IncludesExampleOrTest
__________________________________
Darcs bug tracker <[EMAIL PROTECTED]>
<http://bugs.darcs.net/issue672>
__________________________________
_______________________________________________
darcs-devel mailing list
darcs-devel@darcs.net
http://lists.osuosl.org/mailman/listinfo/darcs-devel
