[
https://issues.apache.org/jira/browse/IGNITE-933?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15907621#comment-15907621
]
ASF GitHub Bot commented on IGNITE-933:
---------------------------------------
GitHub user javaller opened a pull request:
https://github.com/apache/ignite/pull/1615
IGNITE-933
Changed timeout to 500. Test completes successfully on single core machine
as well as on multi-core servers.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/javaller/ignite master
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/1615.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 #1615
----
commit 8e64009ecc2e960db3cfdb5ce900962f17d07982
Author: javaller <2w3e4r5t>
Date: 2017-03-13T14:58:42Z
IGNITE-933
Changed timeout to 500. Test completes successfully on single core machine
as well as on multi-core servers.
----
> GridFailFastNodeFailureDetectionSelfTest.testFailFast fails periodically
> ------------------------------------------------------------------------
>
> Key: IGNITE-933
> URL: https://issues.apache.org/jira/browse/IGNITE-933
> Project: Ignite
> Issue Type: Bug
> Components: general, newbie
> Affects Versions: sprint-5
> Reporter: Denis Magda
> Assignee: Vadim Opolski
> Labels: newbie
>
> The timeout for latch (500 millis) seems to be not enough for some machines.
> Investigate and fix appropriately.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
