beam-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <>
Subject [jira] [Commented] (BEAM-1543) TestPipeline: @Rule error message confusing/javadoc doesn't explain proper usage
Date Thu, 23 Feb 2017 22:19:44 GMT


ASF GitHub Bot commented on BEAM-1543:

GitHub user staslev opened a pull request:

    [BEAM-1543] Updated TestPipeline's javadoc.

    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 BEAM-1543-TestPipeline-javadoc-update

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 #2089
commit a07eea11981fc77994f33c7f0c460aeaec0748ab
Author: Stas Levin <>
Date:   2017-02-23T22:02:14Z

    Updated TestPipeline's javadoc.


> TestPipeline: @Rule error message confusing/javadoc doesn't explain proper usage
> --------------------------------------------------------------------------------
>                 Key: BEAM-1543
>                 URL:
>             Project: Beam
>          Issue Type: Bug
>          Components: sdk-java-core
>            Reporter: Stephen Sisk
>            Assignee: Stas Levin
> I'm working on JdbcIOIT. Trying to run the checked-in version, I encountered this error:

> "Attempted to run a pipeline while it's enforcement level was not set. Are you using
TestPipeline without a @Rule annotation?"
> This error does not give me enough information to diagnose:
> a) what problem is occurring
> b) what I can do to solve it
> Checking the javadocs for TestPipeline, I don't see any information about @Rule or anything
of that nature.
> I did some github blame-ing on that string, and found BEAM-1205 and the accompanying
PR, however it was also unclear from BEAM-1205 exactly what I'm supposed to do to make this
test work.

This message was sent by Atlassian JIRA

View raw message