Closed Bug 978363 Opened 11 years ago Closed 11 years ago

RabbitMQCrashStorage failure in integration test

Categories

(Socorro :: General, task)

task
Not set
blocker

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: rhelmer, Assigned: lars)

Details

Attachments

(1 file)

This has been failing for socorro-release as well as leeroy builds all day:

(from https://ci.mozilla.org/job/socorro-release/933/console)

09:46:38 2014-02-28 09:46:31,923 ERROR - QueuingThread -  - QueuingThread - RabbitMQCrashStorage tried to acknowledge crash 1234689, which was not in the cache
09:46:38 2014-02-28 09:46:31,924 ERROR - QueuingThread -  - QueuingThread - RabbitMQCrashStorage tried to acknowledge crash 06a0c9b5-0381-42ce-855a-ccaaa2120116, which was not in the cache
09:46:38 ERROR: errors found in processor.log
09:46:38 INFO: Purging rabbitmq queue
This is preventing leeroy jobs as well as release builds from happening, it's kind of a big deal :)
Severity: normal → blocker
There were 9 unACKed messages in socorro-jenkins/socorro.priority

I deleted the priority queue to clean it out
Assignee: nobody → lars
Commit pushed to master at https://github.com/mozilla/socorro

https://github.com/mozilla/socorro/commit/fe2ae0091901d568f88a6093727a444d877bb51e
Merge pull request #1926 from twobraids/rabbit-offal

fixes Bug 978363 - ensure rabbitmq is empty before doing any tests that touch it
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Target Milestone: --- → 77
this was merged and completed in 76
Target Milestone: 77 → 76
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: