You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@tajo.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2014/11/15 12:01:33 UTC

[jira] [Commented] (TAJO-1179) Integration tests in TravisCI are occasionally failed due to log size.

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

ASF GitHub Bot commented on TAJO-1179:
--------------------------------------

GitHub user hyunsik opened a pull request:

    https://github.com/apache/tajo/pull/245

    TAJO-1179: Integration tests in TravisCI are occasionally failed due to ...

    ...log size.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/hyunsik/tajo TAJO-1179

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/tajo/pull/245.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 #245
    
----
commit 693bdc0015914f6435048120beb284a5ac81d45a
Author: Hyunsik Choi <hy...@apache.org>
Date:   2014-11-15T11:00:45Z

    TAJO-1179: Integration tests in TravisCI are occasionally failed due to log size.

----


> Integration tests in TravisCI are occasionally failed due to log size.
> ----------------------------------------------------------------------
>
>                 Key: TAJO-1179
>                 URL: https://issues.apache.org/jira/browse/TAJO-1179
>             Project: Tajo
>          Issue Type: Bug
>          Components: build
>            Reporter: Hyunsik Choi
>            Assignee: Hyunsik Choi
>             Fix For: 0.9.1
>
>
> See the q&a at http://stackoverflow.com/questions/26082444/how-to-work-around-travis-cis-4mb-output-limit.
> TravisCI has a limitation of log size. If the log size exceeds 4MB or some threshold line number, the test is terminated by TravisCI as failure.
> So, we need to adjust the log level.



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