GitHub user tgroh opened a pull request:
https://github.com/apache/incubator-beam/pull/361
Add NeedsRunner, annotate core SDK Tests
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).
---
Core SDK tests that require a runner to run cannot be executed while
building the Core SDK, as all runners depend on the Core SDK to be
built. Instead, defer the execution of these tests until the direct
runner is built, and execute them with it on the classpath.
Also relocate Illegal Mutation Tests.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/tgroh/incubator-beam needs_runner_category
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/incubator-beam/pull/361.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 #361
----
commit 43fa956720d2b8eab4fd1487b542e21c9e614717
Author: Thomas Groh <[email protected]>
Date: 2016-05-20T01:52:54Z
Add NeedsRunner, annotate core SDK Tests
Core SDK tests that require a runner to run cannot be executed while
building the Core SDK, as all runners depend on the Core SDK to be
built. Instead, defer the execution of these tests until the direct
runner is built, and execute them with it on the classpath.
commit af72ff61c0aa38b968b1f32514bf609a20c49bc5
Author: Thomas Groh <[email protected]>
Date: 2016-05-20T01:56:55Z
Move ParDo mutation detection tests to runners/direct-java
This is a runner-specific fail-fast behavior.
----
---
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 [email protected] or file a JIRA ticket
with INFRA.
---
