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

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

GitHub user eminency opened a pull request:

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

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

    Currently, state variable is exposed directly to outside.
    Thus, changing state operation is out of locking scope and consistency may 
be broken.
    
    Changing state should be protected by acquiring write lock.

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/451.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 #451
    
----
commit 0c0cb5b9092050de8403ba4b00636acba885b89d
Author: Jongyoung Park <[email protected]>
Date:   2015-03-23T02:14:03Z

    Changing state should be protected by lock acquiring

commit 302ebf7a154c9f3830ab3480ae821127774475bf
Author: Jongyoung Park <[email protected]>
Date:   2015-03-23T02:20:15Z

    Debugging code is removed

----


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