GitHub user alex-filatov opened a pull request:

    https://github.com/apache/beam/pull/3714

    [BEAM-2684] Fix flaky AmqpIOTest

    Source of the flakiness is a race between sender and receiver. In a 
peer-to-peer mode receiver must be running before sender starts sending 
messages. When this's not the case sender gets stuck in a 'send' method. AMQP 
broker solves the problem by eliminating sender/receiver startup order 
requirement.
    
     - [x] Make sure there is a [JIRA 
issue](https://issues.apache.org/jira/projects/BEAM/issues/) filed for the 
change (usually before you start working on it).  Trivial changes like typos do 
not require a JIRA issue.  Your pull request should address just this issue, 
without pulling in other changes.
     - [x] Each commit in the pull request should have a meaningful subject 
line and body.
     - [x] Format the pull request title like `[BEAM-XXX] Fixes bug in 
ApproximateQuantiles`, where you replace `BEAM-XXX` with the appropriate JIRA 
issue.
     - [x] Write a pull request description that is detailed enough to 
understand what the pull request does, how, and why.
     - [x] Run `mvn clean verify` to make sure basic checks pass. A more 
thorough check will be performed on your pull request automatically.
     - [ ] If this contribution is large, please file an Apache [Individual 
Contributor License Agreement](https://www.apache.org/licenses/icla.pdf).
    
    ---


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

    $ git pull https://github.com/alex-filatov/beam 
beam-2684-fix-flaky-amqpiotest

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

    https://github.com/apache/beam/pull/3714.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 #3714
    
----
commit d9456d6f4f2055d76e7e4f47263d5a8019137944
Author: Alex Filatov <alex-fila...@users.noreply.github.com>
Date:   2017-08-10T20:02:37Z

    [BEAM-2684] Fix flaky AmqpIOTest.
    
    Source of the flakiness is a race between sender and receiver. In a 
peer-to-peer mode receiver must be running before sender starts sending 
messages. When this's not the case sender gets stuck in a 'send' method. AMQP 
broker solves the problem by eliminating sender/receiver startup order 
requirement.

----


---
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 infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Reply via email to