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

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

GitHub user eminency opened a pull request:

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

    TAJO-1440: Some tests fail in parallel test environment in TestKillQuery

    To trigger CI, I re-create.

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

    $ git pull https://github.com/eminency/tajo TAJO-1440

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

    https://github.com/apache/tajo/pull/472.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 #472
    
----
commit 0a334d2ad81d111fbc4c435275e9aa9ee9711497
Author: Jongyoung Park <[email protected]>
Date:   2015-03-27T06:58:25Z

    MockAsyncDispatcher added and synchronze by CountDownLatch

----


> 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)

Reply via email to