On 18/04/14 17:52, Matt Welland wrote:
> Just FYI, I'm seeing this kind of message quite often. This is due to
> overlapping clone operations on large fossils on relatively slow disk.
[---]
> Artifacts sent: 0 received: 895 Error: Database error: database is locked:
> {UPDATE event SET mtime=(SELECT m1 FROM time_fudge WHERE mid=objid) WHERE
> objid IN (SELECT mid FROM time_fudge);} <#key_3_2>That error is the reason I had to switch over to the git port of the netbsd fossil repository. First I thought it was a fossil-on-bsd-problem, but I got it on Linux as well. As you say, it is highly reproducible, but it requires quite a bit of time to trigger sometimes. I'm not running on NFS, but I get the exact same behavior. -- Kind Regards, Jan _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
