logging throws error from deactivated builds

[ryanjoneil@…]

When I deactivate a build configuration and then attempt to run existing configurations, I get this error:

2006-08-23 16:17:09,977 [bitten.queue] DEBUG: Checking for pending builds...
2006-08-23 16:18:44,987 [bitten.beep] DEBUG: Scheduling event _enqueue_builds to run at 2006-08-23 16:20:44.987450
2006-08-23 16:18:45,069 [bitten.beep] DEBUG: Scheduling event _initiate_builds to run at 2006-08-23 16:19:09.069690
Traceback (most recent call last):
  File "/usr/lib/python2.4/logging/__init__.py", line 731, in emit
    msg = self.format(record)
  File "/usr/lib/python2.4/logging/__init__.py", line 617, in format
    return fmt.format(record)
  File "/usr/lib/python2.4/logging/__init__.py", line 405, in format
    record.message = record.getMessage()
  File "/usr/lib/python2.4/logging/__init__.py", line 276, in getMessage
    msg = msg % self.args
TypeError: not enough arguments for format string
2006-08-23 16:19:10,070 [bitten.queue] DEBUG: Checking for pending builds...

Apparently the logging module swallows errors in some cases, this one included. A bit of digging brought me to:

...
File "build/bdist.linux-x86_64/egg/bitten/queue.py", line 133, in get_next_pending_build
...

Patch included ;)

[ryan]

Not sure what happened to my title here. Should be: 'logging throws error from deactivated builds'

[cmlenz]

Patch applied in [379].