GitHub user uce opened a pull request:
https://github.com/apache/flink/pull/1708
[FLINK-3500] [test] Fix possible instability in ExecutionGraphRestartTest
After restart of the execution graph, the test driver waits for the graph
to assign the new executions in a loop. If `switchToRunning()` is called
multiple times in this loop, the job is canceled. This could happen, if one
execution had its resource assigned and called `switchToRunning()`, but the
other didn't. In this case, the complete loop was retried and
`switchToRunning()` was called again.
At least, that is the only explanation I could come up with.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/uce/flink 3500-graph_test
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/flink/pull/1708.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #1708
----
commit 5b2a9a8f81843adc8a958ea16417ad46f776afa6
Author: Ufuk Celebi <u...@apache.org>
Date: 2016-02-24T19:39:37Z
[FLINK-3500] [test] Fix possible instability in ExecutionGraphRestartTest
After restart of the execution graph, the test driver waits for the
graph to assign the new executions in a loop. If switchToRunning()
is called multiple times in this loop, the job is canceled. This
could happen, if one execution had its resource assigned and called
switchToRunning(), but the other didn't. In this case, the complete
loop was retried and switchToRunning() was called again.
----
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
