You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@beam.apache.org by "Kyle Weaver (Jira)" <ji...@apache.org> on 2021/05/27 22:24:00 UTC
[jira] [Comment Edited] (BEAM-12320)
PubsubTableProviderIT.testSQLSelectsArrayAttributes[0] failing in SQL
PostCommit
[ https://issues.apache.org/jira/browse/BEAM-12320?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17352784#comment-17352784 ]
Kyle Weaver edited comment on BEAM-12320 at 5/27/21, 10:23 PM:
---------------------------------------------------------------
I was able to repro this on commit 4565a3139554849d6d55680e13827bdb19321476, the first commit for this test. So it has been flaky from the beginning.
With the original 60s timeout on resultSignal.waitForSuccess, the test sometimes failed because the SUCCESS signal was sent, but it didn't have enough time to be processed. With the timeout raised to 600s, that should be fixed. Instead, the test failed because only 2 out of the 3 expected messages were received by the predicate, so the predicate was not fulfilled and the SUCCESS signal was never sent. (To be precise, here is the patch I tested on: [https://github.com/apache/beam/commit/efb2cbdf9473af2988b0641725c1112c31fd8979])
The failure seems to happen for every payload format – we've seen failures for all of JSON, Avro, and Proto.
was (Author: ibzib):
I was able to repro this on commit 4565a3139554849d6d55680e13827bdb19321476, the first commit for this test. So it has been flaky from the beginning.
With the original 60s timeout on resultSignal.waitForSuccess, the test failed because the SUCCESS signal was sent, but it didn't have enough time to be processed. With the timeout raised to 600s, the test failed because only 2 out of the 3 expected messages were received by the predicate, so the predicate was not fulfilled and the SUCCESS signal was never sent. (To be precise, here is the patch I tested on: https://github.com/apache/beam/commit/efb2cbdf9473af2988b0641725c1112c31fd8979)
The failure seems to happen for every payload format – we've seen failures for all of JSON, Avro, and Proto.
> PubsubTableProviderIT.testSQLSelectsArrayAttributes[0] failing in SQL PostCommit
> --------------------------------------------------------------------------------
>
> Key: BEAM-12320
> URL: https://issues.apache.org/jira/browse/BEAM-12320
> Project: Beam
> Issue Type: Bug
> Components: dsl-sql, test-failures
> Reporter: Brian Hulette
> Assignee: Kyle Weaver
> Priority: P1
> Fix For: Not applicable
>
> Time Spent: 1h 40m
> Remaining Estimate: 0h
>
> Failing since https://ci-beam.apache.org/job/beam_PostCommit_SQL/6260/
> {code}
> java.lang.AssertionError: Did not receive signal on projects/apache-beam-testing/subscriptions/result-subscription--1731534761628855545 in 60s
> at org.apache.beam.sdk.io.gcp.pubsub.TestPubsubSignal.pollForResultForDuration(TestPubsubSignal.java:341)
> at org.apache.beam.sdk.io.gcp.pubsub.TestPubsubSignal.waitForSuccess(TestPubsubSignal.java:288)
> at org.apache.beam.sdk.extensions.sql.meta.provider.pubsub.PubsubTableProviderIT.testSQLSelectsArrayAttributes(PubsubTableProviderIT.java:256)
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)