[Buildbot-devel] added horizons to config, pruning causes exception

Johnathan Hegge qdev at oceanhills.net
Wed Oct 9 14:31:23 UTC 2013


You are correct, the line is long, it wasn't displaying and vim jumped a bit too.  Here's the line, trunc'd for sanity:

2013-10-07 16:47:39-0500 [-] while pruning changes
	Traceback (most recent call last):
	  File "/usr/local/lib/python2.7/threading.py", line 781, in __bootstrap
	    self.__bootstrap_inner()
	  File "/usr/local/lib/python2.7/threading.py", line 808, in __bootstrap_inner
	    self.run()
	  File "/usr/local/lib/python2.7/threading.py", line 761, in run
	    self.__target(*self.__args, **self.__kwargs)
	--- <exception caught here> ---
	  File "/opt/PythonEnvs/py27/lib/python2.7/site-packages/twisted/python/threadpool.py", line 191, in _worker
	    result = context.call(ctx, function, *args, **kwargs)
	  File "/opt/PythonEnvs/py27/lib/python2.7/site-packages/twisted/python/context.py", line 118, in callWithContext
	    return self.currentContext().callWithContext(ctx, func, *args, **kw)
	  File "/opt/PythonEnvs/py27/lib/python2.7/site-packages/twisted/python/context.py", line 81, in callWithContext
	    return func(*args,**kw)
	  File "/opt/PythonEnvs/py27/lib/python2.7/site-packages/buildbot/db/pool.py", line 183, in __thd
	    rv = callable(arg, *args, **kwargs)
	  File "/opt/PythonEnvs/py27/lib/python2.7/site-packages/buildbot/db/changes.py", line 200, in thd
	    table.delete(table.c.changeid.in_(ids_to_delete)))
	  File "/opt/PythonEnvs/py27/lib/python2.7/site-packages/sqlalchemy/engine/base.py", line 1449, in execute
	    params)
	  File "/opt/PythonEnvs/py27/lib/python2.7/site-packages/sqlalchemy/engine/base.py", line 1584, in _execute_clauseelement
	    compiled_sql, distilled_params
	  File "/opt/PythonEnvs/py27/lib/python2.7/site-packages/sqlalchemy/engine/base.py", line 1698, in _execute_context
	    context)
	  File "/opt/PythonEnvs/py27/lib/python2.7/site-packages/sqlalchemy/engine/base.py", line 1691, in _execute_context
	    context)
	  File "/opt/PythonEnvs/py27/lib/python2.7/site-packages/sqlalchemy/engine/default.py", line 331, in do_execute
	    cursor.execute(statement, parameters)
	sqlalchemy.exc.OperationalError: (OperationalError) too many SQL variables u'DELETE FROM scheduler_changes WHERE scheduler_changes.changeid IN (?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, 

…. lots of numbers...

 99, 98, 97, 96, 95, 94, 93, 92, 91, 90, 89, 88, 87, 86, 85, 84, 83, 82, 81, 80, 79, 78, 77, 76, 75, 74, 73, 72, 71, 70, 69, 68, 67, 66, 65, 64, 63, 62, 61, 60, 59, 58, 57, 56, 55, 54, 53, 52, 51, 50, 49, 48, 47, 46, 45, 44, 43, 42, 41, 40, 39, 38, 37, 36, 35, 34, 33, 32, 31, 30, 29, 28, 27, 26, 25, 24, 23, 22, 21, 20, 19, 18, 17, 16, 15, 14, 13, 12, 11, 10, 9, 8, 7, 6, 5, 4, 3, 2, 1)

I did copy the master dir and upgrade to 0.8.8 in Python 2.7.5 virtualenv -- time to deal with upgrading WithProperties -- and ran once without horizons.   Clean.  Uncommented and ran again with the horizons.  The pruning looks good -- several rotated logs of cleanup.   I did notice though that state.sqlite is still the same size (3.8MB).   Is that correct?  My few test builds look fine, just expected a trimmed sqlite file.  


On Oct 8, 2013, at 8:32 PM, Dustin J. Mitchell <dustin at v.igoro.us> wrote:

> It looks like you left out the actual exception - the next line of the
> logfile.  Can you pull that out of the logs?
> 
> Dustin





More information about the devel mailing list