beam-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From tgroh <...@git.apache.org>
Subject [GitHub] incubator-beam pull request #886: Make WriteTest more resilient to Randomnes...
Date Thu, 25 Aug 2016 22:01:31 GMT
GitHub user tgroh opened a pull request:

    https://github.com/apache/incubator-beam/pull/886

    Make WriteTest more resilient to Randomness

    Be sure to do all of the following to help us incorporate your contribution
    quickly and easily:
    
     - [ ] Make sure the PR title is formatted like:
       `[BEAM-<Jira issue #>] Description of pull request`
     - [ ] Make sure tests pass via `mvn clean verify`. (Even better, enable
           Travis-CI on your fork and ensure the whole test matrix passes).
     - [ ] Replace `<Jira issue #>` in the title with the actual Jira issue
           number, if there is one.
     - [ ] If this contribution is large, please file an Apache
           [Individual Contributor License Agreement](https://www.apache.org/licenses/icla.txt).
    
    ---
    
    In the worst case scenario for random key assignment in
    Write.ApplyShardingKey, the chance of the number of records per output
    shard was too high. This makes the test significantly less likely to
    flake.

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

    $ git pull https://github.com/tgroh/incubator-beam balance_resilience

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

    https://github.com/apache/incubator-beam/pull/886.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 #886
    
----
commit ebafc8154ce8d2ad981e060042a74858e1a419ce
Author: Thomas Groh <tgroh@google.com>
Date:   2016-08-25T21:58:56Z

    Make WriteTest more resilient to Randomness
    
    In the worst case scenario for random key assignment in
    Write.ApplyShardingKey, the chance of the number of records per output
    shard was too high. This makes the test significantly less likely to
    flake.

----


---
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