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

ASF GitHub Bot commented on IGNITE-10491:
-----------------------------------------

GitHub user akalash opened a pull request:

    https://github.com/apache/ignite/pull/5552

    IGNITE-10491 added test to investigate max threads

    

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

    $ git pull https://github.com/gridgain/apache-ignite ignite-10491

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

    https://github.com/apache/ignite/pull/5552.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 #5552
    
----
commit cc380b5c0aaf49fa6ef2bce0aaf50e303fbefa86
Author: Anton Kalashnikov <kaa.dev@...>
Date:   2018-11-30T13:07:23Z

    IGNITE-14091 added test to max threads

commit aa0a2a6755eafd6e456db7af3f69d6e47fa47de4
Author: Anton Kalashnikov <kaa.dev@...>
Date:   2018-11-30T14:20:04Z

    IGNITE-10491 added bash check

commit df89f0b81781114ca1ee6d704c1a87cd83eea789
Author: Anton Kalashnikov <kaa.dev@...>
Date:   2018-11-30T14:42:31Z

    IGNITE-10491 systemout to log

commit d1939f40987b04bccd7d41f50ff93d44fff0f869
Author: Anton Kalashnikov <kaa.dev@...>
Date:   2018-12-03T08:30:18Z

    IGNITE-10491 return threads test

----


>  Out of memory: unable to create new native thread(test150Clients)
> ------------------------------------------------------------------
>
>                 Key: IGNITE-10491
>                 URL: https://issues.apache.org/jira/browse/IGNITE-10491
>             Project: Ignite
>          Issue Type: Bug
>            Reporter: Anton Kalashnikov
>            Assignee: Anton Kalashnikov
>            Priority: Major
>
> IgniteCache150ClientsTest.test150Clients
> https://ci.ignite.apache.org/viewLog.html?buildId=2424817&tab=buildResultsDiv&buildTypeId=IgniteTests24Java8_Cache6



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

Reply via email to