Closed Bug 1106362 Opened 10 years ago Closed 10 years ago

new resultset messages are not being sent to pulse?

Categories

(Tree Management :: Treeherder: API, defect)

Product:
Tree Management
Component:
Treeherder: API
Platform:
x86
macOS
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED WORKSFORME

People

(Reporter: jlal, Unassigned)

References

Details

Binding 'exchange/treeherder-stage/v1/new-result-set' but not getting any results? This was working a few days ago.
This is still an issue... gandt and I have been listening for messages for a while now and there is nothing.
Earlier this morning garndt said he managed to get a single very out-dated message.


Note, we should probably add a test to treeherder that tests that messages get published.
As message publication happens in a background celary job. I'm not entirely sure how to test this.
For reference the pulse message was added in bug 1016117.
This is a consequence of bug 1110131. I'm working on it
Depends on: 1110131
This should be working now, can you please confirm you are receiving the messages on your side?
You can use the pulse inspector tool to check that messages are published:
https://tools.taskcluster.net/pulse-inspector/#!%28%28exchange:exchange/treeherder-stage/v1/new-result-set,routingKeyPattern:%23%29%29

I see messages arriving... I can't quiet get it to match the UI, but maybe it's just catching up.
Works now the messages are arriving (though slowly at times)
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.