Closed Bug 1300343 Opened 9 years ago Closed 9 years ago

Intermittent-infra HTTPError: HTTP Error 500: Internal Server Error

Categories

(Release Engineering :: Applications: MozharnessCore, defect)

Product:
Release Engineering
Component:
Applications: MozharnessCore
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: intermittent-bug-filer, Unassigned)

References

Details

(Keywords: intermittent-failure)

Filed by: philringnalda [at] gmail.com https://treeherder.mozilla.org/logviewer.html#?job_id=3027842&repo=autoland https://queue.taskcluster.net/v1/task/FQrWVQBQTyaZ9BoNklzImA/runs/0/artifacts/public%2Flogs%2Flive_backing.log Given that you probably can't cause q.tc.n to never under any circumstances throw 500s, a decent alternative would be swallowing the traceback noise and retrying.
See Also: → 1300663
hmm, seems we need to instrument mozharness to print headers, payload and url for the error (this request was redirected, the URLs wasn't printed). And yes, if 5xx and connection errors aren't retried downloads won't be reliable. So automatic retries is probably the fix here.
Component: General → Mozharness
Product: Taskcluster → Release Engineering
QA Contact: jlund
Depends on: 1300812
Summary: Intermittent HTTPError: HTTP Error 500: Internal Server Error → Intermittent-infra HTTPError: HTTP Error 500: Internal Server Error
This was fixed by bug 1300812
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.