Closed
Bug 1174559
Opened 9 years ago
Closed 9 years ago
[docker-worker] Provide treeherder parseable error message when aborting a task
Categories
(Taskcluster :: Workers, defect)
Taskcluster
Workers
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: garndt, Assigned: garndt)
References
Details
Attachments
(1 file)
When tasks are aborted, an error message is appended to the task log, but it's not in a format that TH recognized. In 1174557 a regex was added for lines starting with "[taskcluster] Error:". Update docker-worker to work with this. Right now it's just "[taskcluster] <some message>"
Assignee | ||
Updated•9 years ago
|
Status: NEW → ASSIGNED
Assignee | ||
Comment 1•9 years ago
|
||
Attachment #8622142 -
Flags: review?(jopsen)
Assignee | ||
Comment 2•9 years ago
|
||
Also part of this was moving the logger to be created on 'link' instead of 'created' to ensure it's available
Comment 3•9 years ago
|
||
I got this from the sheriffs mailing list, before this I was not aware there is a Tree Herder API for reporting errors, maybe this is an interesting option, not sure...
On Thu, Jun 11, 2015 at 12:56 PM, Jonathan Griffin <jgriffin@mozilla.com> wrote:
Hi all,
As you know, TaskCluster currently sort of fakes buildbot-style logs so that Treeherder can parse them. Treeherder supports the ability for TC to directly submit all the job/error information via an API, so it wouldn't have to parse TC logs at all, but this would require some extra work on the TC side.
I'm trying to evaluate the priority of that work. Do we see a lot of problems related to parsing of TaskCluster logs that would theoretically be addressed if TC started posting all of the job and error information directly to Treeherder? Or is it more a matter of little paper cuts?
Thanks for any feedback,
Jonathan
_______________________________________________
Sheriffs mailing list
Sheriffs@mozilla.org
https://mail.mozilla.org/listinfo/sheriffs
Assignee | ||
Comment 4•9 years ago
|
||
:pmoore Thanks for adding this. We definitely should make use of this for some things. Such as when a task has run and deadline has been exceeded. I'm wondering if some way the deadline resolver (or something else) could post the error to TH when this happens.
In this instance, it was easy to just add the word "Error: " to something we were logging anyways to hopefully give some info for the sheriffs.
Comment 5•9 years ago
|
||
Comment on attachment 8622142 [details]
PR 105
Looks smart to me...
Attachment #8622142 -
Flags: review?(jopsen) → review+
Assignee | ||
Comment 6•9 years ago
|
||
Assignee | ||
Updated•9 years ago
|
Status: ASSIGNED → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
Updated•9 years ago
|
Component: TaskCluster → Docker-Worker
Product: Testing → Taskcluster
Updated•6 years ago
|
Component: Docker-Worker → Workers
You need to log in
before you can comment on or make changes to this bug.
Description
•