curator-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From cammckenzie <...@git.apache.org>
Subject [GitHub] curator pull request: CURATOR-254 - Modified the test assertions s...
Date Mon, 31 Aug 2015 23:20:14 GMT
GitHub user cammckenzie opened a pull request:

    https://github.com/apache/curator/pull/101

    CURATOR-254 - Modified the test assertions so that they ensure that t…

    …he theoretical maximum queue size is not exceeded. The previous limit was exceedable
depending on how quick consumers were pulling data off the queue.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/apache/curator CURATOR-254

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/curator/pull/101.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #101
    
----
commit 970bd3963cdca545580460e34ccaead8e9c212f7
Author: Cam McKenzie <cammckenzie@apache.org>
Date:   2015-08-31T23:13:06Z

    CURATOR-254 - Modified the test assertions so that they ensure that the theoretical maximum
queue size is not exceeded. The previous limit was exceedable depending on how quick consumers
were pulling data off the queue.

----


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

Mime
View raw message