Frequent "Log could not be found" errors trying to view logs for TaskCluster jobs

RESOLVED FIXED

Status

RESOLVED FIXED
4 years ago
3 years ago

People

(Reporter: RyanVM, Unassigned)

Tracking

Details

(Reporter)

Description

4 years ago
One of example (of many):
https://treeherder.mozilla.org/logviewer.html#?job_id=1583546&repo=b2g-inbound

Not sure if this belongs as a TC or TH bug, but I know that it's making sheriffing the jobs a pretty bad experience.
Flags: needinfo?(jlal)
I think this is a TH bug but I can probably fix it after a bit of debugging...
Okay- the issue here was even though we passed a log the log _must_ have a specific name to show up in the logviewer I worked around this on the server side by changing the name (https://treeherder.allizom.org/logviewer.html#?job_id=2651951&repo=try)
Status: NEW → RESOLVED
Last Resolved: 4 years ago
Flags: needinfo?(jlal)
Resolution: --- → FIXED
Comment hidden (Treeherder Robot)
Component: TaskCluster → General
Product: Testing → Taskcluster
Target Milestone: --- → mozilla41
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.