You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@tajo.apache.org by "Jinho Kim (JIRA)" <ji...@apache.org> on 2014/11/04 09:03:33 UTC

[jira] [Updated] (TAJO-1032) Improve TravisCI scripts to adjust log4j log level

     [ https://issues.apache.org/jira/browse/TAJO-1032?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jinho Kim updated TAJO-1032:
----------------------------
      Component/s: test
    Fix Version/s: 0.9.1
       Issue Type: Task  (was: Bug)

> Improve TravisCI scripts to adjust log4j log level
> --------------------------------------------------
>
>                 Key: TAJO-1032
>                 URL: https://issues.apache.org/jira/browse/TAJO-1032
>             Project: Tajo
>          Issue Type: Task
>          Components: build, test
>            Reporter: Hyunsik Choi
>            Assignee: Jinho Kim
>            Priority: Minor
>             Fix For: 0.9.1
>
>
> Since Travi CI limits the size of standard output log up to 4MB, our Travis CI script prints out only selected lines of unit tests by using grep command. Although this manner limits the output log size, it makes error diagnosis very hard. So, we need to solve it.
> One suggestion is to adjust the log level of log4j used for unit tests instead of grep commend. I expect that this manner will limit the log size as well as make error diagnosis easier.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)