Closed
Bug 1238158
Opened 9 years ago
Closed 9 years ago
builds failing in mozharness in upload_files | _taskcluster_upload
Categories
(Release Engineering :: Applications: MozharnessCore, defect)
Release Engineering
Applications: MozharnessCore
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: aryx, Unassigned)
Details
E.g. https://treeherder.mozilla.org/logviewer.html#?job_id=19524941&repo=mozilla-inbound
Uncaught exception: Traceback (most recent call last):
File "c:\builds\moz2_slave\m-in-w32-d-0000000000000000000\scripts\mozharness\base\script.py", line 1721, in run
self.run_action(action)
File "c:\builds\moz2_slave\m-in-w32-d-0000000000000000000\scripts\mozharness\base\script.py", line 1663, in run_action
self._possibly_run_method(method_name, error_if_missing=True)
File "c:\builds\moz2_slave\m-in-w32-d-0000000000000000000\scripts\mozharness\base\script.py", line 1604, in _possibly_run_method
return getattr(self, method_name)()
File "c:\builds\moz2_slave\m-in-w32-d-0000000000000000000\scripts\mozharness\mozilla\building\buildbase.py", line 1599, in upload_files
property_conditions=property_conditions)
File "c:\builds\moz2_slave\m-in-w32-d-0000000000000000000\scripts\mozharness\mozilla\building\buildbase.py", line 1489, in _taskcluster_upload
task = tc.create_task(routes)
File "c:\builds\moz2_slave\m-in-w32-d-0000000000000000000\scripts\mozharness\mozilla\taskcluster_helper.py", line 65, in create_task
}, taskId=self.task_id)
File "c:\builds\moz2_slave\m-in-w32-d-0000000000000000000\build\venv\Lib\site-packages\taskcluster\client.py", line 455, in apiCall
return self._makeApiCall(e, *args, **kwargs)
File "c:\builds\moz2_slave\m-in-w32-d-0000000000000000000\build\venv\Lib\site-packages\taskcluster\client.py", line 232, in _makeApiCall
return self._makeHttpRequest(entry['method'], route, payload)
File "c:\builds\moz2_slave\m-in-w32-d-0000000000000000000\build\venv\Lib\site-packages\taskcluster\client.py", line 382, in _makeHttpRequest
superExc=rerr
TaskclusterConnectionError: ('Failed to establish connection', SSLError(SSLError(SSLError(8, '_ssl.c:504: EOF occurred in violation of protocol'),),))
Trunk and release branches are closed due to this.
Latest information from #taskcluster is that something in heroku got upgraded and our python versions are too old to use the newly upgraded heroku's SSL. Jonasfj is working on getting the Heroku changes reverted.
Severity: normal → blocker
Looks like the heroku change was reverted and some retriggers are coming back green now. I'll reopen the trees once we get closer to seeing what landed while things were broken.
Reopened.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
| Comment hidden (Intermittent Failures Robot) |
You need to log in
before you can comment on or make changes to this bug.
Description
•