[
https://issues.apache.org/jira/browse/TAJO-1032?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14195868#comment-14195868
]
Hudson commented on TAJO-1032:
------------------------------
SUCCESS: Integrated in Tajo-master-build #435 (See
[https://builds.apache.org/job/Tajo-master-build/435/])
TAJO-1032: Improve TravisCI scripts to adjust log4j log level. (jinho) (jhkim:
rev 080f4e1454fb8dfabe1c15e58d3c1eff8ecd6f6d)
* .travis.yml
* CHANGES
* tajo-core/src/test/java/org/apache/tajo/TajoTestingCluster.java
> 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)
