You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@beam.apache.org by tgroh <gi...@git.apache.org> on 2017/03/23 18:21:25 UTC
[GitHub] beam pull request #2305: Make testShiftTimestampInvalid NeedsRunner instead ...
GitHub user tgroh opened a pull request:
https://github.com/apache/beam/pull/2305
Make testShiftTimestampInvalid NeedsRunner instead of ROS
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).
---
Currently broken in Apex. I'm investigating.
@jkff @tweise
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/tgroh/beam apex-shift-timestamp-invalid
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/beam/pull/2305.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 #2305
----
commit 109a5ba647ec32e971c42a69ace99aefcc4dd8fb
Author: Thomas Groh <tg...@google.com>
Date: 2017-03-23T17:24:39Z
Make testShiftTimestampInvalid NeedsRunner instead of ROS
Currently broken in Apex.
----
---
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.
---