On Mon, Aug 15, 2011 at 1:54 AM, Christopher Vance <[email protected]>wrote:
> I'm using fossil 1.18 [d5bc072296] 2011-07-13 23:40:29 on MacOS (64 > bits), OpenBSD (32 bits), and Linux (32 and 64 bits on different > machines). I have a local clone of the fossil repo for fossil itself, > with one extra (make) file committed and a small number of my own > tickets. I pull from an official repos daily, so the commit number is > presumably relevant only here, but the date should be indicative of > which 'release' version I used. > > After prompting to rebuild the local repo I find that the rebuild has > been running extraordinarily slowly. > > One attempt to fix this was to stop the MacOS rebuild, rebuild a > theoretically identical repo on another machine (they regularly pull > from each other, since I've had no success with sync over ssh), and > copy the result over the MacOS file. The other rebuild completed > within a few seconds, but I still had a rebuild prompt on MacOS after > the copy. The subsequent rebuild on MacOS has been running for more > than 20 hours. > A rebuild should never run for that long. Have you tried running "sqlite3 fossil.fossil 'PRAGMA integrity_check'" on the repository database (which I assume you are calling "fossil.fossil" - substitute whatever name you are using if different). How about "fossil test-integrity"? > > Any suggestions? Any other information I can provide? > > -- > Christopher Vance > _______________________________________________ > fossil-users mailing list > [email protected] > http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users > -- D. Richard Hipp [email protected]
_______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
