geda-developers team mailing list archive
-
geda-developers team
-
Mailing list archive
-
Message #00201
Re: Fixing the git commit robot - bad credentials?
On Thu, 2014-03-13 at 22:11 +0400, Vladimir Zhbanov wrote:
> The last message I got from the robot today:
>
> remote: Bug update database is busy.. (will wait up to two minutes)
> remote: Traceback (most recent call last):
> remote: File "/geda/commit_robot/commit_robot_post-receive.py", line 472, in <module>
> remote: sys.exit(main()
> remote: File "/geda/commit_robot/commit_robot_post-receive.py", line 351, in main
> remote: db = robot_db(robot_db_file)
> remote: File "/geda/commit_robot/commit_robot_post-receive.py", line 138, in __init__
> remote: self._dbcur.execute ("BEGIN EXCLUSIVE")
> remote: sqlite3.OperationalError: database is locked)
>
Make sure all the commit robot processes are terminated, then try
opening the file with the sqlite command line tool "sqlite3". If it
doesn't open - perhaps the DB file is corrupted, or left locked somehow.
--
Peter Clifton <peter.clifton@xxxxxxxxxxxxxxxxxxxxxxxxx>
Clifton Electronics
References