[jira] [Commented] (FLINK-1690) ProcessFailureBatchRecoveryITCase.testTaskManagerProcessFailure spuriously fails on Travis
[
https://issues.apache.org/jira/browse/FLINK-1690?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14541692#comment-14541692
]
Stephan Ewen commented on FLINK-1690:
-
I think this one is stable by now...
ProcessFailureBatchRecoveryITCase.testTaskManagerProcessFailure spuriously
fails on Travis
--
Key: FLINK-1690
URL: https://issues.apache.org/jira/browse/FLINK-1690
Project: Flink
Issue Type: Bug
Reporter: Till Rohrmann
Priority: Minor
I got the following error on Travis.
{code}
ProcessFailureBatchRecoveryITCase.testTaskManagerProcessFailure:244 The
program did not finish in time
{code}
I think we have to increase the timeouts for this test case to make it
reliably run on Travis.
The log of the failed Travis build can be found
[here|https://api.travis-ci.org/jobs/53952486/log.txt?deansi=true]
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (FLINK-1690) ProcessFailureBatchRecoveryITCase.testTaskManagerProcessFailure spuriously fails on Travis
[
https://issues.apache.org/jira/browse/FLINK-1690?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14521669#comment-14521669
]
Robert Metzger commented on FLINK-1690:
---
Another instance https://travis-ci.org/apache/flink/jobs/60670489
ProcessFailureBatchRecoveryITCase.testTaskManagerProcessFailure spuriously
fails on Travis
--
Key: FLINK-1690
URL: https://issues.apache.org/jira/browse/FLINK-1690
Project: Flink
Issue Type: Bug
Reporter: Till Rohrmann
Priority: Minor
I got the following error on Travis.
{code}
ProcessFailureBatchRecoveryITCase.testTaskManagerProcessFailure:244 The
program did not finish in time
{code}
I think we have to increase the timeouts for this test case to make it
reliably run on Travis.
The log of the failed Travis build can be found
[here|https://api.travis-ci.org/jobs/53952486/log.txt?deansi=true]
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (FLINK-1690) ProcessFailureBatchRecoveryITCase.testTaskManagerProcessFailure spuriously fails on Travis
[
https://issues.apache.org/jira/browse/FLINK-1690?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14521736#comment-14521736
]
Stephan Ewen commented on FLINK-1690:
-
This one is interesting, it is not Test specific, it is a vulnerability that
all tests have: A TaskManager port conflict.
Because the port is chosen not by netty, but beforehand (randomly), two
TaskManagers can attempt to open the same port (with a small probability).
ProcessFailureBatchRecoveryITCase.testTaskManagerProcessFailure spuriously
fails on Travis
--
Key: FLINK-1690
URL: https://issues.apache.org/jira/browse/FLINK-1690
Project: Flink
Issue Type: Bug
Reporter: Till Rohrmann
Priority: Minor
I got the following error on Travis.
{code}
ProcessFailureBatchRecoveryITCase.testTaskManagerProcessFailure:244 The
program did not finish in time
{code}
I think we have to increase the timeouts for this test case to make it
reliably run on Travis.
The log of the failed Travis build can be found
[here|https://api.travis-ci.org/jobs/53952486/log.txt?deansi=true]
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (FLINK-1690) ProcessFailureBatchRecoveryITCase.testTaskManagerProcessFailure spuriously fails on Travis
[
https://issues.apache.org/jira/browse/FLINK-1690?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14357144#comment-14357144
]
Stephan Ewen commented on FLINK-1690:
-
I retract my statement. After careful log defusing with [~uce], I think that
things go as planned.
The test has actually a too limited time budget. It takes almost 8 seconds on
my machine, so I grant it that Travis may not be able to complete it in 30
seconds.
ProcessFailureBatchRecoveryITCase.testTaskManagerProcessFailure spuriously
fails on Travis
--
Key: FLINK-1690
URL: https://issues.apache.org/jira/browse/FLINK-1690
Project: Flink
Issue Type: Bug
Reporter: Till Rohrmann
Priority: Minor
I got the following error on Travis.
{code}
ProcessFailureBatchRecoveryITCase.testTaskManagerProcessFailure:244 The
program did not finish in time
{code}
I think we have to increase the timeouts for this test case to make it
reliably run on Travis.
The log of the failed Travis build can be found
[here|https://api.travis-ci.org/jobs/53952486/log.txt?deansi=true]
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (FLINK-1690) ProcessFailureBatchRecoveryITCase.testTaskManagerProcessFailure spuriously fails on Travis
[
https://issues.apache.org/jira/browse/FLINK-1690?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14357098#comment-14357098
]
Till Rohrmann commented on FLINK-1690:
--
This is actually worse.
ProcessFailureBatchRecoveryITCase.testTaskManagerProcessFailure spuriously
fails on Travis
--
Key: FLINK-1690
URL: https://issues.apache.org/jira/browse/FLINK-1690
Project: Flink
Issue Type: Bug
Reporter: Till Rohrmann
Priority: Minor
I got the following error on Travis.
{code}
ProcessFailureBatchRecoveryITCase.testTaskManagerProcessFailure:244 The
program did not finish in time
{code}
I think we have to increase the timeouts for this test case to make it
reliably run on Travis.
The log of the failed Travis build can be found
[here|https://api.travis-ci.org/jobs/53952486/log.txt?deansi=true]
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (FLINK-1690) ProcessFailureBatchRecoveryITCase.testTaskManagerProcessFailure spuriously fails on Travis
[
https://issues.apache.org/jira/browse/FLINK-1690?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14357146#comment-14357146
]
Stephan Ewen commented on FLINK-1690:
-
I will create a patch with increased timeout...
ProcessFailureBatchRecoveryITCase.testTaskManagerProcessFailure spuriously
fails on Travis
--
Key: FLINK-1690
URL: https://issues.apache.org/jira/browse/FLINK-1690
Project: Flink
Issue Type: Bug
Reporter: Till Rohrmann
Priority: Minor
I got the following error on Travis.
{code}
ProcessFailureBatchRecoveryITCase.testTaskManagerProcessFailure:244 The
program did not finish in time
{code}
I think we have to increase the timeouts for this test case to make it
reliably run on Travis.
The log of the failed Travis build can be found
[here|https://api.travis-ci.org/jobs/53952486/log.txt?deansi=true]
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
