[
https://issues.apache.org/jira/browse/TAJO-1440?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14383492#comment-14383492
]
Tajo QA commented on TAJO-1440:
-------------------------------
{color:green}*+1 overall.*{color} Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12707708/TAJO-1440_2.patch
against master revision release-0.9.0-rc0-222-gb1e174e.
{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:green}+1 findbugs.{color} The patch does not introduce any 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/666//testReport/
Console output: https://builds.apache.org/job/PreCommit-TAJO-Build/666//console
This message is automatically generated.
> Some tests fail in parallel test environment in TestKillQuery
> -------------------------------------------------------------
>
> Key: TAJO-1440
> URL: https://issues.apache.org/jira/browse/TAJO-1440
> Project: Tajo
> Issue Type: Bug
> Components: test
> Affects Versions: 0.10.0
> Reporter: Jongyoung Park
> Assignee: Jongyoung Park
> Priority: Blocker
> Attachments: TAJO-1440.log.bz2, TAJO-1440.patch, TAJO-1440_2.patch
>
>
> Running following command, test process often fails.
> bq. mvn clean install -Pparallel-test,hcatalog-0.12.0 -DLOG_LEVEL=ERROR
> -Dmaven.fork.count=2
> But it is not 100% failure rate.
> It looks like a concurrency problem.
> The reason why is :
> # When INFO instead of ERROR for log level is used, it doesn't seem that it
> happens.
> # Only it happens in parallel test.
> Usual failure spot is at TestKillQuery.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
