[
https://issues.apache.org/jira/browse/BEAM-10761?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kenneth Knowles updated BEAM-10761:
-----------------------------------
Resolution: Fixed
Status: Resolved (was: Resolved)
Hello! Due to a bug in our Jira configuration, this issue had status:Resolved
but resolution:Unresolved.
I am bulk editing these issues to have resolution:Fixed
If a different resolution is appropriate, please change it. To do this, click
the "Resolve" button (you can do this even for closed issues) and set the
Resolution field to the right value.
> Add TestPubsub.waitForSubscription
> ----------------------------------
>
> Key: BEAM-10761
> URL: https://issues.apache.org/jira/browse/BEAM-10761
> Project: Beam
> Issue Type: Improvement
> Components: io-java-gcp, testing
> Reporter: Brian Hulette
> Assignee: Brian Hulette
> Priority: P2
> Fix For: Not applicable
>
> Time Spent: 3h 40m
> Remaining Estimate: 0h
>
> We have several tests that rely on TestPubsubSignal.signalStart as an
> imperfect signal that a pipeline has created a subscription to a PubSub
> topic, and it is safe for us to start injecting data. This has the potential
> to be flaky.
> We should instead poll pubsub until we can observe a subscription was
> created. This can be implemented via a method TestPubsub.waitForSubscription
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
