[
https://issues.apache.org/jira/browse/BEAM-3056?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16204145#comment-16204145
]
Valentyn Tymofieiev commented on BEAM-3056:
-------------------------------------------
This may be what happens here: Dataflow job started by testE2EWordCount test
does not produce expected results. The test waits for the job to produce
expected results within one hour, and then fails, for example:
https://builds.apache.org/job/beam_PreCommit_Java_MavenInstall/15061/console.
However in some cases, due to different timings, the whole test suite fails
because 150 min timeout is exceeded while waiting for the same test suite to
complete. This is what happened in precommit runs in mentioned in the first
message on the thread.
> Java precommit tests on Jenkins run too slow, delaying commits.
> ---------------------------------------------------------------
>
> Key: BEAM-3056
> URL: https://issues.apache.org/jira/browse/BEAM-3056
> Project: Beam
> Issue Type: Bug
> Components: testing
> Reporter: Valentyn Tymofieiev
> Assignee: Jason Kuster
>
> Here's an example of two instances where the issue affected me in the last
> few days.
> The test suite consistently made progress, then timed out after 150 min.
> https://builds.apache.org/job/beam_PreCommit_Java_MavenInstall/15044/consoleFull
> https://builds.apache.org/job/beam_PreCommit_Java_MavenInstall/15037/consoleFull
> What are our options here, besides increasing the timeout?
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
