[
https://issues.apache.org/jira/browse/BEAM-5779?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16657103#comment-16657103
]
Udi Meiri commented on BEAM-5779:
---------------------------------
I think the error in 6321 is similar in nature: the job was cancelled
(successfully this time) before it managed to process and write the expected
output.
> Failure in beam_PostCommit_Python_Verify PubSubIntegrationTest on Dataflow
> --------------------------------------------------------------------------
>
> Key: BEAM-5779
> URL: https://issues.apache.org/jira/browse/BEAM-5779
> Project: Beam
> Issue Type: Bug
> Components: sdk-py-core
> Reporter: Kenneth Knowles
> Assignee: Udi Meiri
> Priority: Major
> Labels: flake
> Time Spent: 20m
> Remaining Estimate: 0h
>
> https://builds.apache.org/job/beam_PostCommit_Python_Verify/6296/
> Path to failure:
> * (Jenkins) beam_PostCommit_Python_Verify
> * (gradle) :beam-sdks-python:postCommitITTests
> * (py module) test_streaming_data_only
> * (test class)
> apache_beam.io.gcp.pubsub_integration_test.PubSubIntegrationTest
> {code}
> AssertionError:
> Expected: (Test pipeline expected terminated in state: RUNNING and Expected 2
> messages.)
> but: Expected 2 messages. Got 0 messages. Diffs (item, count):
> Expected but not in actual: [('data002-seen', 1), ('data001-seen', 1)]
> Unexpected: []
> {code}
> Looks like a legitimate failure. It is flakey as it went green later.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
