1456484 - Only prefix errors with [taskcluster:error]

Status: RESOLVED INCOMPLETE

(Taskcluster :: Workers, enhancement, P5)

Description

[Dustin J. Mitchell [:dustin] (he/him)]

From bug 1453622:

* Tone down the [taskcluster:error] printing for exceptions - if every single exception prints the line "[taskcluster:error] Task not successful due to following exception(s):" for any exception then Treeherder will suggest any bug which includes that in the summary for every single exception, and since a reftest run where a single test fails, and then the suite returns 1 and then the exit code for the run is massaged to Exit Code 2 and a non-zero exit code is an exception, you have this and every other intermittent-failure bug which includes that string suggested for every run with one reftest test failing, and if it's suggested then people will take that suggestion, whether or not doing so is reasonable. If in the block of log lines:

[taskcluster:error] Task not successful due to following exception(s):
[taskcluster:error] Exception 1)
[taskcluster:error] zip: not a valid zip file
[taskcluster:error] 

the only one which is actually a taskcluster error is "zip: not a valid zip file" then the others (both the ones that are noise repeated in every failure and fer gossake the blank line) are not a taskcluster:error, and should instead be prefixed with whatever's used for [taskcluster:noise] or [taskcluster:throat-clearing].

Comment 1

[Dustin J. Mitchell [:dustin] (he/him)]

I think treeherder has gotten a lot better at parsing these messages since this was filed.