Closed Bug 986116 Opened 11 years ago Closed 11 years ago

Task graph error UI?

Categories

(Taskcluster :: General, defect)

Product:
Taskcluster
Component:
General
Platform:
x86
macOS
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: jlal, Unassigned)

Details

While working on the task graph hookup for gaia one thing that came up is what happens when there is an error posting the graph? Ideally we can report some detailed errors if the syntax of the graph/task is invalid. One though I had is to build an "error ui" which has a fixed endpoint (url) which we can point users at... This could be as simple as a payload uploaded to S3 (as json) which we can have a viewer for... Right now if there is an error it's up to the endpoint which submitted the graph to deal with it... This is not terrible but will come up with all graph consumers so it would be nice to have some helpers around this.
Okay, I see how this would be nice... but skip the viewer step (for now)... Just dump error into a file on S3, provide a link to the file on treeherder and call it a day. From the JSON error it's pretty obvious what is wrong. (Note, to self, we should add a UUID to 500 errors, then we can search loggly for uuid when somebody reports an internal server error). The errors provided by the queue doesn't have any specified format at this point. When they do we can talk about this again. But for now let's just assume that it's somewhat human readable JSON :)
@lightsofapollo, Is there any specific request in this bug... or should we close it? I don't follow the request entirely, do you want the queue/scheduler to create an error page on S3 whenever an error occurs? IMO, the error could also just be base64 encoded and added to the #hash for a url to somewhere that'll display that error as JSON. Again we have no formal error format.
Flags: needinfo?(jlal)
Lets close this for now... with artifact errors and the support the worker has for dumping json schema errors I am happy for now.
Status: NEW → RESOLVED
Closed: 11 years ago
Flags: needinfo?(jlal)
Resolution: --- → FIXED
Component: TaskCluster → General
Product: Testing → Taskcluster
Target Milestone: --- → mozilla41
Version: unspecified → Trunk
Resetting Version and Target Milestone that accidentally got changed...
Target Milestone: mozilla41 → ---
Version: Trunk → unspecified
You need to log in before you can comment on or make changes to this bug.