[Sending again this time with the trace as a zipped attachment, and *not* inline; sorry. It's got through to [EMAIL PROTECTED]; this cc to cvs-ghc is for info.]
More darcs2 woe, this time on Linux. I'm simply merging patches from the cabal repository into my working tree. My working tree is absolutely un-modified, but it's old, so there are 197 patches to pull. Problem is this: Darcs is hung saying "Merging them 64/197". So far it's consumed 8 minutes of CPU time on a fast machine. This is terribly depressing: there is nothing tricky going on here. No local modifications, no conflicts, nothing but a straight pull. Presumably by the time we get to "Merging them" there is no network traffic either. It's just stuck (apparently) in a horribly inefficient algorithm, or an infinite loop. I can't tell which. What should I do now? It's still running (I'm up to 11 mins of CPU now). I'll leave it to run, on the grounds that disturbing it will disturb any evidence you may want me to collect. But I'll kill it in a while. rsvp Simon
darcs-bug-trace.gz
Description: darcs-bug-trace.gz
_______________________________________________ Cvs-ghc mailing list [email protected] http://www.haskell.org/mailman/listinfo/cvs-ghc
