411391 - Fix processor handling of error conditions

Status: RESOLVED FIXED

(Socorro :: General, task)

Description

[Samuel Sidler (old account; do not CC)]

Reported by bsmedberg, Jul 12, 2007

The processor has a rather hodgepodge set of error/success conditions, and
needs to report processing errors more effectively. In particular:

1) missing product/buildid should be fatal
2) error messages from processing should be reported to the log
3) python exceptions from processing should be reported to the log

And this should all be tested.

I'll take this for now, but feel free to steal it if you are inspired

Comment 1

[Michael Morgan [:morgamic]]

Lars, this is lumped in with refactor -- please comment if that is incorrect.

Comment 2

[K Lars Lohn [:lars] [:klohn]]

THe refactoring covers these issues:

> 1) missing product/buildid should be fatal
a dump with missing product/buildid terminates the processing of that dump.  An error is put into the log file.  Bug 421985 addresses putting an explanation of the error into the reports table.

> 2) error messages from processing should be reported to the log
the logging system is configurable as to the severity of errors logged.  Problems in processing a dump are given the error level of WARNING or ERROR.  These are logged iff the system is told to log these errors.

> 3) python exceptions from processing should be reported to the log
python exceptions with tracebacks are given a logging level of ERROR.  They will be logged iff the system is configured to save these messages.