Closed
Bug 1537922
Opened 7 years ago
Closed 6 years ago
add tests to ensure that services fail gracefully when a pulse message cannot be sent
Categories
(Taskcluster :: Services, enhancement)
Taskcluster
Services
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: dustin, Assigned: dustin, Mentored)
Details
We just had a big 'ol pulse outage, meaning that lots of publisher.someMessage(..) calls failed.
Let's test that circumstance everywhere we send a message, and ensure that the behavior is known and as good as we can make it.
| Assignee | ||
Comment 1•6 years ago
|
||
This would still be something useful to test, having just had another outage :/
Assignee: nobody → dustin
| Assignee | ||
Comment 2•6 years ago
|
||
| Assignee | ||
Comment 3•6 years ago
|
||
https://github.com/taskcluster/taskcluster/pull/2317
Just queue left. I kind of want to stop staring at this bug in my task list!
| Assignee | ||
Comment 4•6 years ago
|
||
..and queue just got a production workout of this functionality this morning. It seems to work (I mean, it spews 500's, but it works..)!
| Assignee | ||
Updated•6 years ago
|
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•