[
https://issues.apache.org/jira/browse/TAJO-1449?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14377580#comment-14377580
]
Tajo QA commented on TAJO-1449:
-------------------------------
{color:red}*-1 overall.*{color} Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12706867/TAJO-1449_2.patch
against master revision release-0.9.0-rc0-217-g3e9a2dd.
{color:green}+1 @author.{color} The patch does not contain any @author
tags.
{color:green}+1 tests included.{color} The patch appears to include 2 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 2 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/651//testReport/
Findbugs warnings:
https://builds.apache.org/job/PreCommit-TAJO-Build/651//artifact/incubator-tajo/patchprocess/newPatchFindbugsWarningstajo-core.html
Console output: https://builds.apache.org/job/PreCommit-TAJO-Build/651//console
This message is automatically generated.
> TestSelectQuery.testExplainSelect() fails
> -----------------------------------------
>
> Key: TAJO-1449
> URL: https://issues.apache.org/jira/browse/TAJO-1449
> Project: Tajo
> Issue Type: Bug
> Components: test
> Reporter: Jihoon Son
> Assignee: Jihoon Son
> Priority: Blocker
> Fix For: 0.11.0
>
> Attachments: TAJO-1449.patch, TAJO-1449_2.patch
>
>
> In TAJO-1426, the shape of logical plans for explain statements is fixed
> according to some rules during unit tests. So, the expected result also have
> to be changed, but it doesn't.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
