[
https://issues.apache.org/jira/browse/FLINK-2156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14947402#comment-14947402
]
ASF GitHub Bot commented on FLINK-2156:
---------------------------------------
Github user StephanEwen commented on the pull request:
https://github.com/apache/flink/pull/1234#issuecomment-146299251
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?
> Scala modules cannot create logging file
> ----------------------------------------
>
> Key: FLINK-2156
> URL: https://issues.apache.org/jira/browse/FLINK-2156
> Project: Flink
> Issue Type: Bug
> Components: Build System
> Affects Versions: 0.10
> Reporter: Till Rohrmann
> Labels: starter
> Fix For: 0.10
>
>
> The Scala only modules {{flink-scala-shell}} and {{flink-ml}} use Maven's
> scalatest plugin to run their tests. The scalatest plugin has no
> {{forkNumber}}, though. Therefore, the logging fails to create the logging
> file as specified in the {{log4j-travis.properties}} file.
> We can fix this issue by giving these two modules different
> {{log4j.properties}} files which don't require a {{forkNumber}}. Or we fix
> the {{forkNumber}} to 1.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
