Closed
Bug 1372208
Opened 7 years ago
Closed 7 years ago
Live log updates result in "An error occurred while trying to load the specified log. It may not exist, or may not have any content."
Categories
(Taskcluster :: UI, defect)
Taskcluster
UI
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: whimboo, Unassigned)
Details
I was trying to watch the live log of the following task: https://tools.taskcluster.net/task-inspector/#NCte9krZQZOttUrWaswWaA/0 Sadly after a couple of seconds when it seems to reload data, the following error is displayed: > An error occurred while trying to load the specified log. It may not exist, or may not have any content. This prevents me from actually seeing the log entries I want.
Comment 1•7 years ago
|
||
Is it possible this was because the task resolved as you were watching the livelog? I think the UI should cope with this, and show the backing log once the live log becomes unavailable. Eli, what are your thoughts?
Flags: needinfo?(eperelman)
Comment 2•7 years ago
|
||
My guess is it has something to do with a problem in our handling of the request completing while streaming in our current logviewer implementation. This quarter we are switching to a new logviewer implementation while should hopefully see issues like this no longer occur.
Flags: needinfo?(eperelman)
Comment 3•7 years ago
|
||
Yea, you're streaming data from a location that's specific to that instance and task environment. At some point when the task is completed that stream is closed and the original taskcluster artifact URL is redirect to a new permanent location for the log. Perhaps if there is an error while streaming, it should try refreshing the entire log again from the taskcluster artifact URL, which will then redirect to the correct location.
Reporter | ||
Comment 4•7 years ago
|
||
No, this was not when a task got resolved. It was preparing the environement for mozharness. And each time new data is incoming I got this failure displayed. Reloading the log made it work for a couple of seconds before the next data came in.
Comment 5•7 years ago
|
||
Thanks for the update/clarification Henrik!
Updated•7 years ago
|
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
Reporter | ||
Comment 6•7 years ago
|
||
Eli, by which change (bug) has this been fixed? Thanks
Flags: needinfo?(eperelman)
Comment 7•7 years ago
|
||
https://github.com/taskcluster/taskcluster-tools/commit/b8424aebbbf4bafa34241083a4ba881bf17ced6d
Flags: needinfo?(eperelman)
Reporter | ||
Comment 8•7 years ago
|
||
This looks awesome. Thank you a lot for this work!
Comment 9•7 years ago
|
||
My pleasure!
Assignee | ||
Updated•5 years ago
|
Component: Tools → UI and Tools
You need to log in
before you can comment on or make changes to this bug.
Description
•