Closed Bug 1227879 Opened 10 years ago Closed 9 years ago

Intermittent [taskcluster:error] Error calling 'stopped' for artifactHandler : Encountered error when uploading artifact(s)

Categories

(Taskcluster :: General, defect)

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

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: nigelb, Assigned: wcosta)

References

(
URL
)

Details

(Keywords: intermittent-failure)

https://treeherder.mozilla.org/logviewer.html#?job_id=17802327&repo=mozilla-inbound ========= Finished Build ./build-emulator-x86.sh /home/worker/workspace (results: 0, elapsed: 3389 secs) (at 2015-10-25 08:22:38.882000) ========= [taskcluster] === Task Finished === [taskcluster:error] Error uploading "public/build/emulator.tar.gz" artifact. connect ETIMEDOUT [taskcluster:error] Error calling 'stopped' for artifactHandler : Encountered error when uploading artifact(s) [taskcluster] Unsuccessful task run with exit code: -1 completed in 3653.314 seconds
This is the #2 intermittent orange over the past 3 days. It would be helpful to get this assigned appropriately (whether that's a fix in Taskcluster or better diagnostics that would lead to a fix elsewhere).
Flags: needinfo?(sdeckelmann)
This has already been assigned and being worked on by Wander Costa (wcosta) under this bug 1186619. We just finished putting through its final paces today and addressing some final comments.
Assignee: nobody → wcosta
Status: NEW → ASSIGNED
Depends on: 1186619
This seem to have stopped once bug 1186619 was deployed. Thanks!
Status: ASSIGNED → RESOLVED
Closed: 9 years ago
Flags: needinfo?(sdeckelmann)
Resolution: --- → FIXED
There was a moment in time last week where there were some issues with the queue that caused this. It returned to normal and hasn't been starred since.
(In reply to Selena Deckelmann :selenamarie :selena from comment #27) > This seem to have stopped once bug 1186619 was deployed. Thanks! It doesn't look so and sheriffs still star failures against this bug. So I assume we should reopen given that no real fix has been landed via this bug.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
This spiked again yesterday. garndt: anyone that could help us know what happened? This link also shows the last spike at the end of August: https://brasstacks.mozilla.com/orangefactor/?display=Bug&bugid=1227879&startday=2016-08-30&endday=2016-09-26&tree=all
Flags: needinfo?(garndt)
We're investigating this as the current cause of a tree closure Working hypothesis is that this is caused by the auth service running out of RAM and failing, which (because everything depends on it) causes everything to fail.
Flags: needinfo?(garndt)
I think this was just a symptom of the treeclosure, the root of which was bug 1305828. That cause may have been "building" for a while and caused the increase Armen observed.
Looking at orange factor [1] I think it's clear that this issue has been resolved by fixing the underlying auth issues. [1] https://brasstacks.mozilla.com/orangefactor/?display=Bug&bugid=1227879&startday=2016-09-27&endday=2016-09-29&tree=all
Status: REOPENED → RESOLVED
Closed: 9 years ago → 9 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.