The internal log reporting for scan failures is currently very obtuse. It could do with adding a stack trace to the error shown. This is very easy by doing something like this:
=== modified file 'lib/lp/buildmaster/manager.py' --- lib/lp/buildmaster/manager.py 2009-07-26 14:19:49 +0000 +++ lib/lp/buildmaster/manager.py 2009-12-14 20:46:44 +0000 @@ -238,6 +238,7 @@ """Deal with scanning failures.""" self.logger.info( 'Scanning failed with: %s' % error.getErrorMessage()) + error.printTraceback() self.finishCycle()
The internal log reporting for scan failures is currently very obtuse. It could do with adding a stack trace to the error shown. This is very easy by doing something like this:
=== modified file 'lib/lp/ buildmaster/ manager. py' buildmaster/ manager. py 2009-07-26 14:19:49 +0000 buildmaster/ manager. py 2009-12-14 20:46:44 +0000
self. logger. info(
' Scanning failed with: %s' % error.getErrorM essage( )) eback()
self. finishCycle( )
--- lib/lp/
+++ lib/lp/
@@ -238,6 +238,7 @@
"""Deal with scanning failures."""
+ error.printTrac