Skip to content

Conversation

@dcorbacho
Copy link
Contributor

Proposed Changes

Move some quorum queue tests to a generic queue type suite.

Added more tests for basic.cancel which must NOT return unacked messages to the queue as implemented by quorum queues. Fixes this too.

Types of Changes

  • Bug fix (non-breaking change which fixes issue #NNNN)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause an observable behavior change in existing systems)
  • Documentation improvements (corrections, new content, etc)
  • Cosmetic change (whitespace, formatting, etc)

Checklist

  • I have read the CONTRIBUTING.md document
  • I have signed the CA (see https://cla.pivotal.io/sign/rabbitmq)
  • All tests pass locally with my changes
  • I have added tests that prove my fix is effective or that my feature works
  • I have added necessary documentation (if appropriate)
  • Any dependent changes have been merged and published in related repositories

Additional tests for basic.cancel which must NOT return unacked
messages to the queue as implemented by quorum queues.
It's not part of the spec. Messages should stay unacked as the consumer
can still ack them, it simply won't receive new messages.
Consumer state should be kept if unacked messages are present, but not listed.
@dcorbacho dcorbacho requested a review from kjnilsson February 11, 2019 17:59
Rename rabbit_fifo consumer suspected_down field to status.
@kjnilsson kjnilsson merged commit b0dfe93 into master Feb 12, 2019
@michaelklishin michaelklishin deleted the queues-testing branch March 16, 2019 02:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants