flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FLINK-2156) Scala modules cannot create logging file
Date Wed, 07 Oct 2015 17:54:26 GMT

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

ASF GitHub Bot commented on FLINK-2156:
---------------------------------------

Github user chiwanpark commented on the pull request:

    https://github.com/apache/flink/pull/1234#issuecomment-146277055
  
    BTW, because your PR is based on your master branch, not topic branch, you should [overwrite
master branch in your repository](http://stackoverflow.com/questions/1125968/force-git-to-overwrite-local-files-on-pull)
after this PR is merged.
    
    Creating a topic branch and sending pull request based on the branch are commonly recommended.
:)


> 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)

Mime
View raw message