You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Maxim Muzafarov (JIRA)" <ji...@apache.org> on 2018/03/17 16:13:00 UTC

[jira] [Commented] (IGNITE-4706) Rewrite test GridTaskExecutionSelfTest::testJobIdCollision to use multiple JVMs

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

Maxim Muzafarov commented on IGNITE-4706:
-----------------------------------------

As mentioned Sergey Chugunov on dev-mail:
{quote}Also rewriting the test to multi-JVM fashion isn't an easy task, to me it
is much better to spend this time working on more important stuff.
{quote}

> Rewrite test GridTaskExecutionSelfTest::testJobIdCollision to use multiple JVMs
> -------------------------------------------------------------------------------
>
>                 Key: IGNITE-4706
>                 URL: https://issues.apache.org/jira/browse/IGNITE-4706
>             Project: Ignite
>          Issue Type: Test
>            Reporter: Sergey Chugunov
>            Priority: Minor
>
> h2. Notes
> Test emulates ID collision by tricks with *IgniteUuid* local counter which leads to failures of important components like discovery messaging.
> It makes test unstable; sometimes it hangs or fails in a various ways.
> h2. Acceptance Criteria
> Test exploits multiple JVMs to execute its logic, all tricks with IgniteUuid are removed.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)