When a build step succeeds, the last entry for that step contains the name of the step that succeeded:
   INFO - Step "name of step" run successfully.
However, when a build step fails, the last entry for that step is always:
  ERROR - Build success condition not satisfied.

It would be more useful for debugging, and for parsing of the logs, if the error message named the step that failed. For example, if I run two parallel build tasks, and one of them fails, I end up with:

2006-11-20 10:17:24,141 [Thread-3251] INFO - Triggering step "build data (parallel)".
2006-11-20 10:17:24,157 [Thread-3300] INFO - Triggering step "build client data".
2006-11-20 10:17:24,157 [Thread-3301] INFO - Triggering step "build server data".
2006-11-20 10:17:25,672 [Thread-3303] INFO - data_c > build_client.log
2006-11-20 10:17:25,672 [Thread-3305] INFO - data_s > build_server.log
2006-11-20 12:58:55,494 [Thread-3300] INFO - Step "build client data" run successfully.
2006-11-20 13:37:33,375 [Thread-3301] ERROR - Build success condition not satisfied.
2006-11-20 13:37:33,406 [Thread-3251] ERROR - Composite step "build data (parallel)" failed due to unsatisfication of step success condition.

When I grep for lines containing ERROR and WARN in my Velocity template, I don't find out the name of the object that failed. The only way to find out is to make a much more intelligent log parser, bypassing the builtin QuickBuild functionality. And if I put the above in the notification email, my users squawk, because they don't want to have to think.

But, if I could grep the ERROR lines and get:
  2006-11-20 13:37:33,375 [Thread-3301] ERROR - Step "build server data" failed.
  2006-11-20 13:37:33,406 [Thread-3251] ERROR - Composite step "build data add (parallel)" failed due to unsatisfication of step success condition.
then, we would be cooking with gas!

Thanks,
Don