GitHub user lukecwik opened a pull request:

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

    [BEAM-151] Remove DataflowPipelineRunner refs in TestPipeline/PAssert

    Be sure to do all of the following to help us incorporate your contribution
    quickly and easily:
    
     - [x] Make sure the PR title is formatted like:
       `[BEAM-<Jira issue #>] Description of pull request`
     - [x] Make sure tests pass via `mvn clean verify`. (Even better, enable
           Travis-CI on your fork and ensure the whole test matrix passes).
     - [x] Replace "<Jira issue #>" in the title with the actual Jira issue
           number, if there is one.
     - [x] If this contribution is large, please file an Apache
           [Individual Contributor License 
Agreement](https://www.apache.org/licenses/icla.txt).
    
    ---


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

    $ git pull https://github.com/lukecwik/incubator-beam dataflow-runner-4

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

    https://github.com/apache/incubator-beam/pull/154.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 #154
    
----
commit e403691b01e8deabd424bade0127e873004627f9
Author: Luke Cwik <lc...@google.com>
Date:   2016-04-08T22:07:52Z

    [BEAM-151] Remove dependence on DataflowPipelineRunner in 
PAssert/TestPipeline
    
    Added the ability for TestDataflowPipelineRunner to throw an AssertionError
    when the pipeline fails using the first job error message.
    
    This allows for moving Dataflow to a new package.

commit d84b921176e926cd71c540285f07fd37f921b0ec
Author: Luke Cwik <lc...@google.com>
Date:   2016-04-08T22:49:53Z

    [BEAM-151] Expand javadoc in TestPipeline explaining usage
    
    Update TestDataflowPipelineRunner to capture all the failure messages.

----


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