[ 
https://issues.apache.org/jira/browse/BEAM-7582?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17188867#comment-17188867
 ] 

Brian Hulette commented on BEAM-7582:
-------------------------------------

I just re-enabled the test in https://github.com/apache/beam/pull/12750.

I'll monitor over the next week to see if it increases flakiness, if it does 
I'll @ignore it again and use this jira to track the fix. If it doesn't I'll 
resolve this jira.

I think this particular issue may have been resolved by bumping the pubsub 
client default timeout in https://github.com/apache/beam/pull/11985

> TestPubsub.listSubscriptions is flaky
> -------------------------------------
>
>                 Key: BEAM-7582
>                 URL: https://issues.apache.org/jira/browse/BEAM-7582
>             Project: Beam
>          Issue Type: Improvement
>          Components: dsl-sql
>            Reporter: Rui Wang
>            Assignee: Brian Hulette
>            Priority: P3
>
> o.grpc.StatusRuntimeException: DEADLINE_EXCEEDED: Deadline expired before 
> operation could complete.
> >       at 
> > io.grpc.stub.ClientCalls.toStatusRuntimeException(ClientCalls.java:233)
> >       at io.grpc.stub.ClientCalls.getUnchecked(ClientCalls.java:214)
> >       at io.grpc.stub.ClientCalls.blockingUnaryCall(ClientCalls.java:139)
> >       at 
> > com.google.pubsub.v1.SubscriberGrpc$SubscriberBlockingStub.listSubscriptions(SubscriberGrpc.java:1734)
> >       at 
> > org.apache.beam.sdk.io.gcp.pubsub.PubsubGrpcClient.listSubscriptions(PubsubGrpcClient.java:373)
> >       at 
> > org.apache.beam.sdk.io.gcp.pubsub.TestPubsub.listSubscriptions(TestPubsub.java:165)
> https://builds.apache.org/job/beam_PostCommit_SQL/1843/
> https://builds.apache.org/job/beam_PostCommit_SQL/1842/
> https://builds.apache.org/job/beam_PostCommit_SQL/1841/
> https://builds.apache.org/job/beam_PostCommit_SQL/1840/
> https://builds.apache.org/job/beam_PostCommit_SQL/1839/



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to