Thus said Jan Danielsson on Fri, 02 May 2014 17:39:20 +0200:
> > 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>
> [...]
> As you say, it is highly reproducible, but it requires quite a bit
> of time to trigger sometimes.
This particular error hasn't come up since this checkin (which didn't
make it into Fossil 1.28, so it's only in trunk or on branch-1.28):
http://www.fossil-scm.org/index.html/info/b4dffdac5e706980d911a0e672526ad461ec0640
I wonder if you could try again with a build from trunk?
Thanks,
Andy
--
TAI64 timestamp: 400000005363dc90
_______________________________________________
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
