[
https://issues.apache.org/jira/browse/TAJO-1032?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14195790#comment-14195790
]
ASF GitHub Bot commented on TAJO-1032:
--------------------------------------
GitHub user jinossy opened a pull request:
https://github.com/apache/tajo/pull/226
TAJO-1032: Improve TravisCI scripts to adjust log4j log level
I've change the logging level to 'mvn clean install -DLOG_LEVEL=WARN'
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/jinossy/tajo TAJO-1032
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/tajo/pull/226.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #226
----
commit 9eb88233fedddcc6c06a9ff82b3f43e70483a47e
Author: jhkim <[email protected]>
Date: 2014-11-04T06:32:36Z
TAJO-1032: Improve TravisCI scripts to adjust log4j log level
commit cf47b212aa85156bac75ff121f87e9c1aac9d1f7
Author: jhkim <[email protected]>
Date: 2014-11-04T06:35:16Z
remove double quote
----
> Improve TravisCI scripts to adjust log4j log level
> --------------------------------------------------
>
> Key: TAJO-1032
> URL: https://issues.apache.org/jira/browse/TAJO-1032
> Project: Tajo
> Issue Type: Bug
> Components: build
> Reporter: Hyunsik Choi
> Assignee: Jinho Kim
> Priority: Minor
>
> 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)
