This may be entirely unrelated, but I've just had to re-clone the afp hg repository in my home directory at TUM because it made mercurial crash on pull, and failed integrity checking.
The only other time I've ever had to do that in the past few years of using mercurial was because of file corruption due to a broken hard disk (two cases). If this happens frequently to us, something may be very wrong with storage on the macbroy/lxbroy machines. The only difference in usage I can see to local use at NICTA is that we're usually on fairly fresh versions of mercurial, whereas the various machines at TUM seem to have a mix of less recent versions. We also use NFS less, but we do use it. Cheers, Gerwin On 28/11/2012, at 8:11 PM, Lars Noschinski <nosch...@in.tum.de> wrote: > Hi everyone, > > mira still crashes from time to time. Sometimes, it is not a programming > error, but some external error condition which could maybe be handled more > gracefully: > > Repository update fails: The repository corruptions yesterday and > some time ago caused a failed update (see attachment). Mira could > probabliy just go to sleep and try again later. > > For future changes it might be worth to keep in mind that the Mercurial > project considers the python interface as internal: > > http://mercurial.selenic.com/wiki/MercurialApi > > -- Lars > <repository-corruption.log><repository-corruption-2.log>_______________________________________________ > isabelle-dev mailing list > isabelle-...@in.tum.de > https://mailmanbroy.informatik.tu-muenchen.de/mailman/listinfo/isabelle-dev ________________________________ The information in this e-mail may be confidential and subject to legal professional privilege and/or copyright. National ICT Australia Limited accepts no liability for any damage caused by this email or its attachments. _______________________________________________ isabelle-dev mailing list isabelle-...@in.tum.de https://mailmanbroy.informatik.tu-muenchen.de/mailman/listinfo/isabelle-dev
