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

Matthias edited comment on FLINK-18842 at 9/10/20, 7:41 AM:
------------------------------------------------------------

I discussed the issue with [~rmetzger]: It is hard to debug since it's 
happening within the Docker build. It does not have to be related to the 
{{connection refused}} error that appears since it's also appearing in 
succeeding builds.
I created a new branch which runs this test multiple times trying to reproduce 
the problem without success: 
* [Build 
#38|https://dev.azure.com/mapohl/flink/_build/results?buildId=38&view=logs&j=aba23331-5614-58a0-ecb7-9c9e540c50fe&t=b30be84f-4d76-59f8-beed-6fd3501240e4]
 - 50 runs without any error
* [Build 
#39|https://dev.azure.com/mapohl/flink/_build/results?buildId=39&view=logs&j=1f3ed471-1849-5d3c-a34c-19792af4ad16&t=0d2e35fc-a330-5cf2-a012-7267e2667b1d]
 - 100 runs without any error
* [Build 
#40|https://dev.azure.com/mapohl/flink/_build/results?buildId=40&view=logs&j=1f3ed471-1849-5d3c-a34c-19792af4ad16&t=0d2e35fc-a330-5cf2-a012-7267e2667b1d]
 - 100 runs without any error (the failure was caused by another test that 
tried to download Kafka (cmp. 
[FLINK-19158|https://issues.apache.org/jira/browse/FLINK-19158])

I propose to wait for [~chesnay] to have a look at the issue.


was (Author: mapohl):
I discussed the issue with [~rmetzger]: It is hard to debug since it's 
happening within the Docker build. It does not have to be related to the 
{{connection refused}} error that appears since it's also appearing in 
succeeding builds.
I created a new branch which runs this test multiple times trying to reproduce 
the problem without success: 
* [Build 
#38|https://dev.azure.com/mapohl/flink/_build/results?buildId=38&view=logs&j=aba23331-5614-58a0-ecb7-9c9e540c50fe&t=b30be84f-4d76-59f8-beed-6fd3501240e4]
 - 50 runs without any error
* [Build 
#39|https://dev.azure.com/mapohl/flink/_build/results?buildId=39&view=logs&j=1f3ed471-1849-5d3c-a34c-19792af4ad16&t=0d2e35fc-a330-5cf2-a012-7267e2667b1d]
 - 100 runs without any error
* [Build 
#40|https://dev.azure.com/mapohl/flink/_build/results?buildId=40&view=logs&j=1f3ed471-1849-5d3c-a34c-19792af4ad16&t=0d2e35fc-a330-5cf2-a012-7267e2667b1d]
 - 100 runs without any error (the failure was caused by another test that 
tried to download Kafka (cmp. 
[FLINK-19158|https://issues.apache.org/jira/browse/FLINK-19158])
* 
We're gonna wait for [~chesnay] to have a look at the issue.

> e2e test failed to download "localhost:9999/flink.tgz" in "Wordcount on 
> Docker test"
> ------------------------------------------------------------------------------------
>
>                 Key: FLINK-18842
>                 URL: https://issues.apache.org/jira/browse/FLINK-18842
>             Project: Flink
>          Issue Type: Test
>          Components: flink-docker, Test Infrastructure
>    Affects Versions: 1.11.0
>            Reporter: Dian Fu
>            Assignee: Matthias
>            Priority: Major
>              Labels: test-stability
>
> https://dev.azure.com/apache-flink/apache-flink/_build/results?buildId=5260&view=logs&j=c88eea3b-64a0-564d-0031-9fdcd7b8abee&t=2b7514ee-e706-5046-657b-3430666e7bd9
> {code}
> 2020-08-06T20:51:31.2499580Z + wget -nv -O flink.tgz 
> localhost:9999/flink.tgz
> 2020-08-06T20:51:31.2501498Z 127.0.0.1 - - [06/Aug/2020 20:51:31] "GET 
> /flink.tgz HTTP/1.1" 200 -
> 2020-08-06T20:51:31.2502214Z failed: Connection refused.
> 2020-08-06T20:51:31.6885068Z 2020-08-06 20:51:31 
> URL:http://localhost:9999/flink.tgz [322693675/322693675] -> "flink.tgz" [1]
> 2020-08-06T20:51:31.6888547Z + [ false = true ]
> 2020-08-06T20:51:31.6889384Z + tar -xf flink.tgz --strip-components=1
> 2020-08-06T20:51:34.8125585Z + rm flink.tgz
> 2020-08-06T20:51:34.8699287Z + chown -R flink:flink .
> 2020-08-07T00:20:42.7919165Z 
> 2020-08-07T00:20:43.0365895Z ##[error]The operation was canceled.
> {code}



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

Reply via email to