beam-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From kennknowles <>
Subject [GitHub] beam pull request #2721: [BEAM-2086] Remove TestDataflowRunner reliance on m...
Date Thu, 27 Apr 2017 01:01:36 GMT
GitHub user kennknowles opened a pull request:

    [BEAM-2086] Remove TestDataflowRunner reliance on metrics in streaming

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

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

    $ git pull TestDataflowRunner

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

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

    This closes #2721
commit 1008def0f28c43b8225f68a2a8f713b84b89a485
Author: Kenneth Knowles <>
Date:   2017-04-27T00:55:29Z

    Remove max watermark check from TestDataflowRunner
    The Dataflow service automatically shuts down jobs when their
    input watermarks reach infinity.

commit 35b1147d28471af1a92a938b42702dd9a0c9a98c
Author: Kenneth Knowles <>
Date:   2017-04-27T00:56:05Z

    Do not rely on PAssert metrics in streaming TestDataflowRunner
    These metrics are currently absent. This can be restored when the
    feature is returned to the Dataflow service.


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

View raw message