[
https://issues.apache.org/jira/browse/BEAM-6338?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16732402#comment-16732402
]
Mark Liu commented on BEAM-6338:
--------------------------------
Took a further look at
https://builds.apache.org/job/beam_PostCommit_Python_Verify/6968. The job is
submitted at Jan 2, 2019, 9:51:53 AM, but vm starts at 2019-01-02 (10:02:16).
Since this streaming test has 180s to wait for data processing
([here|https://github.com/apache/beam/blob/master/sdks/python/apache_beam/examples/streaming_wordcount_it_test.py#L94])
and another 400s timeout in PubSub result verifier
([here|https://github.com/apache/beam/blob/master/sdks/python/apache_beam/examples/streaming_wordcount_it_test.py#L91]),
the pipeline was still not ready after those timeout. I don't think we can do
much on the slowness since it's unusual long time for worker startup that
depends on google cloud infrastructure.
> Python streaming test failed because cannot cancel the job
> ----------------------------------------------------------
>
> Key: BEAM-6338
> URL: https://issues.apache.org/jira/browse/BEAM-6338
> Project: Beam
> Issue Type: Test
> Components: test-failures
> Reporter: Boyuan Zhang
> Assignee: Mark Liu
> Priority: Major
>
> apache_beam.examples.streaming_wordcount_it_test.StreamingWordCountIT
> [https://builds.apache.org/job/beam_PostCommit_Python_Verify/6968/]
> https://builds.apache.org/job/beam_PostCommit_Python_Verify/6955/
> Failed to cancel this streaming job since it was not ready to cancel. After
> checking the console log, seems like the runner harness is waiting for sdk.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
