Github user tillrohrmann commented on the pull request:
https://github.com/apache/flink/pull/1234#issuecomment-146449913
FlinkML uses scalatest to run its tests. Scalatest didn't use the fork
number and simply executed all tests sequentially. This shouldn't be a big
problem, because there are only few tests to run.
On Oct 7, 2015 9:13 PM, "Stephan Ewen" <notificati...@github.com> wrote:
> We do execute multiple tests concurrently (multiple forks). Does this lead
> to problems when all forks see the fork number "1" ? I am wondering,
> because at some places, we use the fork number to prevent port conflicts.
>
> Then again, how could these parts have worked before when the fork number
> was missing in the first place?
>
> â
> Reply to this email directly or view it on GitHub
> <https://github.com/apache/flink/pull/1234#issuecomment-146299251>.
>
---
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.
---
