[ 
https://issues.apache.org/jira/browse/FLINK-22110?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Flink Jira Bot updated FLINK-22110:
-----------------------------------
    Labels: stale-major test-stability  (was: test-stability)

I am the [Flink Jira Bot|https://github.com/apache/flink-jira-bot/] and I help 
the community manage its development. I see this issues has been marked as 
Major but is unassigned and neither itself nor its Sub-Tasks have been updated 
for 30 days. I have gone ahead and added a "stale-major" to the issue". If this 
ticket is a Major, please either assign yourself or give an update. Afterwards, 
please remove the label or in 7 days the issue will be deprioritized.


> KinesisTableApiITCase.testTableApiSourceAndSink fails/hangs on Azure when 
> building FlinkContainer
> -------------------------------------------------------------------------------------------------
>
>                 Key: FLINK-22110
>                 URL: https://issues.apache.org/jira/browse/FLINK-22110
>             Project: Flink
>          Issue Type: Bug
>          Components: Connectors / Kinesis
>    Affects Versions: 1.13.0
>            Reporter: Guowei Ma
>            Priority: Major
>              Labels: stale-major, test-stability
>
> https://dev.azure.com/apache-flink/apache-flink/_build/results?buildId=16056&view=logs&j=c88eea3b-64a0-564d-0031-9fdcd7b8abee&t=ff888d9b-cd34-53cc-d90f-3e446d355529&l=27232
> {code:java}
> Apr 06 00:08:58 [ERROR] 
> testTableApiSourceAndSink(org.apache.flink.streaming.kinesis.test.KinesisTableApiITCase)
>   Time elapsed: 0.007 s  <<< ERROR!
> Apr 06 00:08:58 java.lang.RuntimeException: Could not build the flink-dist 
> image
> Apr 06 00:08:58       at 
> org.apache.flink.tests.util.flink.FlinkContainer$FlinkContainerBuilder.build(FlinkContainer.java:280)
> Apr 06 00:08:58       at 
> org.apache.flink.streaming.kinesis.test.KinesisTableApiITCase.<init>(KinesisTableApiITCase.java:77)
> Apr 06 00:08:58       at 
> sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
> Apr 06 00:08:58       at 
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> Apr 06 00:08:58       at 
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> Apr 06 00:08:58       at 
> java.lang.reflect.Constructor.newInstance(Constructor.java:423)
> Apr 06 00:08:58       at 
> org.junit.runners.BlockJUnit4ClassRunner.createTest(BlockJUnit4ClassRunner.java:217)
> Apr 06 00:08:58       at 
> org.junit.runners.BlockJUnit4ClassRunner$1.runReflectiveCall(BlockJUnit4ClassRunner.java:266)
> Apr 06 00:08:58       at 
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> Apr 06 00:08:58       at 
> org.junit.runners.BlockJUnit4ClassRunner.methodBlock(BlockJUnit4ClassRunner.java:263)
> Apr 06 00:08:58       at 
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
> Apr 06 00:08:58       at 
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
> Apr 06 00:08:58       at 
> org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
> Apr 06 00:08:58       at 
> org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
> Apr 06 00:08:58       at 
> org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
> Apr 06 00:08:58       at 
> org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
> Apr 06 00:08:58       at 
> org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
> Apr 06 00:08:58       at 
> org.junit.internal.runners.statements.FailOnTimeout$CallableStatement.call(FailOnTimeout.java:298)
> Apr 06 00:08:58       at 
> org.junit.internal.runners.statements.FailOnTimeout$CallableStatement.call(FailOnTimeout.java:292)
> {code}



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

Reply via email to