Skip to content

fixes Bug 978363 - ensure rabbitmq is empty before doing any tests that touch it #1926

Merged
merged 1 commit into from Mar 1, 2014

2 participants

@twobraids
Mozilla member

I've seen this on vagrant, too. Sometimes when an integration test ends in a failure, there are jobs left hanging around in rabbitmq. These extra jobs are then offered to the processors in the next test run which then violates the expectations of the processor integration test.

This PR makes sure that both the normal and priority queues are empty in the before the integration tests are run. The integration test also tries to clean up afterwards, but if the script ends prematurely, rabbit droppings will be left in the queues. The pre-cleaning will take care of that mess.

@twobraids
Mozilla member

@rhelmer r?
or anyone else that has been hit over the head with this problem.

@lonnen
Mozilla member
lonnen commented Mar 1, 2014

👾

@lonnen lonnen merged commit fe2ae00 into mozilla:master Mar 1, 2014

1 check passed

Details default Jenkins build 'socorro-github' #2905 has succeeded
@lonnen
Mozilla member
lonnen commented Mar 1, 2014

nice branch name

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.