[
https://issues.apache.org/jira/browse/BEAM-1647?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15901762#comment-15901762
]
ASF GitHub Bot commented on BEAM-1647:
--------------------------------------
GitHub user kennknowles opened a pull request:
https://github.com/apache/beam/pull/2197
[BEAM-1647] Bump Dataflow ROS timeout to 120 minutes
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/kennknowles/beam dataflow-timeout
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/beam/pull/2197.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 #2197
----
commit 60c2273cd1231f804c1b7cab33f8867895c44964
Author: Kenneth Knowles <[email protected]>
Date: 2017-03-08T18:47:07Z
Bump Dataflow ROS timeout to 120 minutes
----
> Dataflow RunnableOnService tests timing out reliably
> ----------------------------------------------------
>
> Key: BEAM-1647
> URL: https://issues.apache.org/jira/browse/BEAM-1647
> Project: Beam
> Issue Type: Bug
> Components: runner-dataflow, testing
> Reporter: Kenneth Knowles
> Assignee: Kenneth Knowles
> Priority: Blocker
>
> Since [build
> 2487|https://builds.apache.org/view/Beam/job/beam_PostCommit_Java_RunnableOnService_Dataflow/2487/]
> our build time seems to have pushed up past 1h40m and is timing out.
> It was just barely under that anyhow, so I don't expect this is a
> catastrophic change but probably something small. Some builds (at HEAD) seem
> to sneak under the limit.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
