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

Tajo QA commented on TAJO-1526:
-------------------------------

{color:red}*-1 overall.*{color}  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12723585/TAJO-1526.patch
  against master revision release-0.9.0-rc0-244-gd160f6e.

    {color:green}+1 @author.{color}  The patch does not contain any @author 
tags.

    {color:green}+1 tests included.{color}  The patch appears to include 1 new 
or modified test files.

    {color:green}+1 javac.{color}  The applied patch does not increase the 
total number of javac compiler warnings.

    {color:green}+1 javadoc.{color}  The applied patch does not increase the 
total number of javadoc warnings.

    {color:green}+1 checkstyle.{color}  The patch generated 0 code style errors.

    {color:red}-1 findbugs.{color}  The patch appears to introduce 17 new 
Findbugs (version 2.0.3) warnings.

    {color:green}+1 release audit.{color}  The applied patch does not increase 
the total number of release audit warnings.

    {color:green}+1 core tests.{color}  The patch passed unit tests in 
tajo-core.

Test results: 
https://builds.apache.org/job/PreCommit-TAJO-Build/721//testReport/
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-TAJO-Build/721//artifact/incubator-tajo/patchprocess/newPatchFindbugsWarningstajo-core.html
Console output: https://builds.apache.org/job/PreCommit-TAJO-Build/721//console

This message is automatically generated.

> Investigate the frequent failures of Travis CI
> ----------------------------------------------
>
>                 Key: TAJO-1526
>                 URL: https://issues.apache.org/jira/browse/TAJO-1526
>             Project: Tajo
>          Issue Type: Task
>            Reporter: Jihoon Son
>            Assignee: Jihoon Son
>            Priority: Critical
>         Attachments: TAJO-1526.patch
>
>
> Travis CI is frequently failed in recent days. It seems that the test is 
> killed due to some reaons. Since the test is killed around 
> TestExternalSortExec which writes more than 52 MB, I suspect the write size 
> limit, but am not sure. 
> Here are some logs.
> {noformat}
> ...
> Running org.apache.tajo.engine.planner.physical.TestExternalSortExec
> Run: testLeftOuterJoinWithNull1[3]
> Run: testLeftOuterJoinWithNull2[3]
> Run: testLeftOuterJoinWithNull3[3]
> Run: testRightOuterJoinWithThetaJoinConditionInWhere[3]
> Run: testLeftOuterWithEmptyTable[3]
> Run: testFullOuterJoinPredicationCaseByCase1[3]
> Run: testRightOuterJoin1[3]
> Run: testJoinOnMultipleDatabases[3]
> Run: testFullOuterJoinWithEmptyTable1[3]
> Run: testFullOuterJoinWithEmptyIntermediateData[3]
> Run: testCrossJoinWithThetaJoinConditionInWhere[3]
> Run: testComplexJoinCondition1[3]
> Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 23.036 sec - 
> in org.apache.tajo.engine.planner.physical.TestExternalSortExec
> Running org.apache.tajo.engine.planner.physical.TestTupleSorter
> Run: testComplexJoinCondition2[3]
> Run: testComplexJoinCondition3[3]
> Run: testComplexJoinCondition4[3]
> Run: testComplexJoinCondition5[3]
> Run: testComplexJoinCondition6[3]
> 2015-04-05 17:31:25,478 WARN: 
> org.apache.tajo.engine.planner.global.GlobalPlanner 
> (visitTableSubQuery(1536)) - Can't find left most SubQuery in the UnionNode.
> Run: testComplexJoinCondition7[3]
> 2015-04-05 17:31:27,707 WARN: 
> org.apache.tajo.engine.planner.global.GlobalPlanner 
> (visitTableSubQuery(1536)) - Can't find left most SubQuery in the UnionNode.
> Run: testDifferentTypesJoinCondition[3]
> Run: testComplexJoinsWithCaseWhen[3]
> Run: testJoinWithOrPredicates[3]
> Run: testLeftOuterJoinWithEmptyTable1[3]
> Run: testLeftOuterJoinWithEmptyTable2[3]
> Run: testLeftOuterJoinWithEmptyTable3[3]
> Run: testLeftOuterJoinWithEmptyTable4[3]
> Run: testLeftOuterJoinWithEmptyTable5[3]
> Run: testJoinCoReferredEvals1[3]
> Run: testCrossJoinWithEmptyTable1[3]
> Run: testLeftOuterJoinWithThetaJoinConditionInWhere[3]
> Run: testJoinWithJson2[3]
> Run: testOuterJoinAndCaseWhen1[3]
> Run: testJoinOnMultipleDatabasesWithJson[3]
> Killed
> Run: testInnerJoinWithEmptyTable[3]
> Run: testJoinWithDifferentShuffleKey[3]
> Run: testJoinFilterOfRowPreservedTable1[3]
> ...
> {noformat}
> {noformat}
> ...
> Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 6.096 sec - 
> in org.apache.tajo.engine.planner.physical.TestFullOuterHashJoinExec
> Running org.apache.tajo.engine.planner.physical.TestFullOuterMergeJoinExec
> 2015-04-04 10:10:38,960 WARN: 
> org.apache.tajo.engine.planner.global.GlobalPlanner 
> (visitTableSubQuery(1536)) - Can't find left most SubQuery in the UnionNode.
> Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 10.963 sec - 
> in org.apache.tajo.engine.planner.physical.TestFullOuterMergeJoinExec
> Running org.apache.tajo.engine.planner.physical.TestHashSemiJoinExec
> Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.06 sec - in 
> org.apache.tajo.engine.planner.physical.TestHashSemiJoinExec
> Running org.apache.tajo.engine.planner.physical.TestMergeJoinExec
> Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.037 sec - 
> in org.apache.tajo.engine.planner.physical.TestMergeJoinExec
> Running org.apache.tajo.engine.planner.physical.TestExternalSortExec
> 3000000 rows (52 MB)
> Killed
> Tests run: 316, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 814.466 sec 
> - in org.apache.tajo.engine.query.TestJoinQuery
> Running org.apache.tajo.engine.planner.physical.TestTupleSorter
> Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 37.473 sec - 
> in org.apache.tajo.engine.planner.physical.TestTupleSorter
> Running org.apache.tajo.engine.planner.physical.TestLeftOuterHashJoinExec
> Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 6.753 sec - 
> in org.apache.tajo.engine.planner.physical.TestLeftOuterHashJoinExec
> Running org.apache.tajo.engine.planner.physical.TestHashJoinExec
> ...
> {noformat}



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

Reply via email to