Closed
Bug 1198284
Opened 9 years ago
Closed 9 years ago
Parse taskcluster error and exception messages from task logs that originate from taskcluster components
Categories
(Tree Management :: Treeherder: Data Ingestion, defect)
Tree Management
Treeherder: Data Ingestion
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: garndt, Assigned: garndt)
Details
Attachments
(1 file)
In bug 1174557 there was a regex introduce to parse error messages in the format "^\[taskcluster\] Error:". This worked for some things, but limited the messages to be only [taskcluster] where we have components that log as [tc-vcs]. Also, it relies on "Error:" being the start of the error message, which doesn't always happen or if it does makes some information in the error message redudant. We are switching some of our tooling to log in the format "[component:event] message" such that a taskcluster error could appear as: [taskcluster:error] Some bad message Or in the case of one of our tools: [taskcluster-vcs:error] Bad things happened This bug is to allow any arbitrary component to put something into the logs with an "error" or "exception" event and TH parse that out.
Assignee | ||
Comment 1•9 years ago
|
||
Attachment #8652355 -
Flags: review?(emorley)
Comment 2•9 years ago
|
||
Comment on attachment 8652355 [details] [review] Treeherder PR 905 Thank you! :-)
Attachment #8652355 -
Flags: review?(emorley) → review+
Comment 3•9 years ago
|
||
Commit pushed to master at https://github.com/mozilla/treeherder https://github.com/mozilla/treeherder/commit/ddd2163379e25bb609e1609f80bfa720a1f38055 Bug 1198284 - Add error regex to better match taskcluster errors
Comment 4•9 years ago
|
||
This is also now deployed :-)
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•