[
https://issues.apache.org/jira/browse/BEAM-6510?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16754825#comment-16754825
]
Maximilian Michels commented on BEAM-6510:
------------------------------------------
{quote}
I do notice that the lines 18:54:04 INFO: Unbounded Flink Source 12/16 is
reading from sources: only include 1/16 through 15/16. Not that I have any idea
if that indicates a problem.
{quote}
That is indeed strange. We should see 0-15. The output is a bit misleading
because it is zero-based. However, I see 16 outputs on the first failing build:
https://builds.apache.org/job/beam_PostCommit_Java_Nexmark_Flink/1688/consoleFull
I think I know what is wrong here. The test pipelines do not shutdown correctly
because the default shutdown behavior in streaming mode changed. Should use the
TestFlinkRunner. Will open a PR.
> [beam_PostCommit_Java_Nexmark_Flink] Consistently timing out
> ------------------------------------------------------------
>
> Key: BEAM-6510
> URL: https://issues.apache.org/jira/browse/BEAM-6510
> Project: Beam
> Issue Type: Bug
> Components: test-failures
> Reporter: Daniel Oliveira
> Assignee: Kenneth Knowles
> Priority: Major
> Labels: SQL, currently-failing
>
> _Use this form to file an issue for test failure:_
> * [Jenkins
> Job|https://builds.apache.org/job/beam_PostCommit_Java_Nexmark_Flink/1688/]
> (This is the first instance where it times out.)
> * [Gradle Build Scan|https://scans.gradle.com/s/cnh2qe3m5xbw4]
> Initial investigation:
> Test seems to be timing out without an obvious reason. Strangely, the Gradle
> scans show it succeeding no problem.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
