Closed Bug 1094253 Opened 10 years ago Closed 9 years ago

No pulse notifications for today's builds

Categories

(Mozilla QA Graveyard :: Infrastructure, defect)

Version 2
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: mihaelav, Unassigned)

References

Details

There were some connection timeouts:

2014-11-05T02:20:05Z ERROR:automation:[Errno 110] Connection timed out

error: [Errno 110] Connection timed out
2014-11-05T02:20:05Z INFO:automation:Connecting to Mozilla Pulse as "qa-auto@mozilla.com|mozmill_release|mm-ci-master1.qa.scl3.mozilla.com"...
2014-11-05T02:20:05Z INFO:automation:Connected
2014-11-05T06:17:39Z ERROR:automation:[Errno 110] Connection timed out

error: [Errno 110] Connection timed out
2014-11-05T06:17:39Z INFO:automation:Connecting to Mozilla Pulse as "qa-auto@mozilla.com|mozmill_release|mm-ci-master1.qa.scl3.mozilla.com"...
2014-11-05T06:17:39Z INFO:automation:Connected
2014-11-05T09:28:39Z ERROR:automation:[Errno 110] Connection timed out

error: [Errno 110] Connection timed out
2014-11-05T09:28:39Z INFO:automation:Connecting to Mozilla Pulse as "qa-auto@mozilla.com|mozmill_release|mm-ci-master1.qa.scl3.mozilla.com"...
2014-11-05T09:28:39Z INFO:automation:Connected
2014-11-05T12:04:59Z ERROR:automation:[Errno 110] Connection timed out

error: [Errno 110] Connection timed out
2014-11-05T12:04:59Z INFO:automation:Connecting to Mozilla Pulse as "qa-auto@mozilla.com|mozmill_release|mm-ci-master1.qa.scl3.mozilla.com"...
2014-11-05T12:04:59Z INFO:automation:Connected
2014-11-05T15:30:36Z ERROR:automation:[Errno 110] Connection timed out

error: [Errno 110] Connection timed out
2014-11-05T15:30:36Z INFO:automation:Connecting to Mozilla Pulse as "qa-auto@mozilla.com|mozmill_release|mm-ci-master1.qa.scl3.mozilla.com"...
2014-11-05T15:30:36Z INFO:automation:Connected
Depends on: 1094272
Those timeouts are not related at all. They were less than a second. Usually it should be the task of the ciduty to talk with the pulse devs, but I did it again this time. After a couple of minutes analyzing messages with Mark, we noticed that pulsetranslator is failing in publishing the messages, and does not retry. Mark will file a specific bug for that soon.
Assignee: nobody → hskupin
Status: NEW → ASSIGNED
I want to add, that we missed EVERY build today! It was not only a single one or so, but really all messages for any daily and l10n build, on each branch, and every platform! Mark can hopefully land a bandaid fix later today, so that we can operate safer tomorrow.
There is nothing more I can do here at the moment. We have to wait for the dependencies to be fixed.
Assignee: hskupin → nobody
Status: ASSIGNED → NEW
Whiteboard: [blocked]
Since we disabled SSL for pulsetranslator no other build message was lost. I think we can get this bug closed and keep investigating on the pulsetranslator side.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
Whiteboard: [blocked]
Product: Mozilla QA → Mozilla QA Graveyard
You need to log in before you can comment on or make changes to this bug.