apycot-moved #19162 unreadable logs [resolved]

currently it's hard to read preprocessors/logs file. The most notable pb is that often the information that help to find why something failed is in a separated DEBUG message above the ERROR message.

IMO:

  • ERROR messages due to command failures should hold the debug information
  • when a message do not apply to a particular path in the source, use the path information to hold the command name
  • (moved to #20006) to colorize logs according to severity
  • (moved to #20005)each checker should be responsible to tell why it failed (and add this information to the failure notification mail)
priorityimportant
typebug
done in1.6.0
load1.000
load left0.000
closed by<not specified>

Workflow history

from state (3)to statecommentdateUser
validation pendingresolved2010/10/13 21:09 UTCsthenault
donevalidation pending

version published

2010/02/05 06:23 UTCsthenault
opendone2010/01/26 17:56 UTCpydavid

Comments

  • 2009/12/03 14:43, written by sthenault

    1.5.0 includes most of this but:

    • stylesheet should be completed
    • last item still to implemented
    • each checker messages handling should be reviewed
add comment
tagged by

Ticket #19162 - latest update on 2010/10/13, created on 2009/12/02 by Sylvain Thenault