[
https://issues.apache.org/jira/browse/BEAM-12061?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17313308#comment-17313308
]
Brian Hulette commented on BEAM-12061:
--------------------------------------
Per
https://ci-beam.apache.org/job/beam_PostCommit_SQL/lastCompletedBuild/testReport/junit/org.apache.beam.sdk.extensions.sql.meta.provider.kafka/KafkaTableProviderIT/history/?start=50
it looks like this has been flaking for quite a while.
Earliest I see is
https://ci-beam.apache.org/job/beam_PostCommit_SQL/6063/testReport/junit/org.apache.beam.sdk.extensions.sql.meta.provider.kafka/KafkaTableProviderIT/testFake2_3_/,
but that's pretty close to the oldest run we have right now (6058).
Stacktrace:
{code}
java.lang.AssertionError
at org.junit.Assert.fail(Assert.java:87)
at org.junit.Assert.assertTrue(Assert.java:42)
at org.junit.Assert.assertTrue(Assert.java:53)
at
org.apache.beam.sdk.extensions.sql.meta.provider.kafka.KafkaTableProviderIT.testFake2(KafkaTableProviderIT.java:152)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at
org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:59)
...
{code}
> beam_PostCommit_SQL failing on KafkaTableProviderIT.testFakeNested
> ------------------------------------------------------------------
>
> Key: BEAM-12061
> URL: https://issues.apache.org/jira/browse/BEAM-12061
> Project: Beam
> Issue Type: Bug
> Components: dsl-sql
> Reporter: Kenneth Knowles
> Assignee: Robin Qiu
> Priority: P1
> Labels: currently-failing, flake
>
> The failures in the SQL postcommit started at
> https://ci-beam.apache.org/view/PostCommit/job/beam_PostCommit_SQL/6092/
> There are no changes indicated in that build, so it seems likely to be
> infrastructure/environment or a flake that just got unlucky.
> Some error messages about being unable to contact broker, but I didn't look
> deeply as I wanted first to file a bug to track.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
