You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Ilya Kasnacheev (Jira)" <ji...@apache.org> on 2020/03/16 15:42:00 UTC
[jira] [Comment Edited] (IGNITE-12663) Let's limit all thread
pools' sizes to 5 in tests
[ https://issues.apache.org/jira/browse/IGNITE-12663?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17060310#comment-17060310 ]
Ilya Kasnacheev edited comment on IGNITE-12663 at 3/16/20, 3:41 PM:
--------------------------------------------------------------------
[~ascherbakov] I think that we should add explicit tests for varying thread pool sizes, if you think that's important.
I don't see any value if test will be flaky depending on the hardware configuration. It would doubtfully lead to any fixes, but may lead to false negatives - ignored failures in flaky suites.
was (Author: ilyak):
[~ascherbakov] I think that we should add explicit tests for varying thread pool sizes.
I don't see any value if test will be flaky depending on the hardware configuration. It would doubtfully lead to any fixes, but may lead to false negatives - ignored failures in flaky suites.
> Let's limit all thread pools' sizes to 5 in tests
> -------------------------------------------------
>
> Key: IGNITE-12663
> URL: https://issues.apache.org/jira/browse/IGNITE-12663
> Project: Ignite
> Issue Type: Test
> Reporter: Ilya Kasnacheev
> Assignee: Ilya Kasnacheev
> Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> The rationale is, it is very painful shoving through thread dumps of test with N CPU threads in every pool.
> Why 5? Rebalance thread pool is 4 by default, and system pool has to be bigger
--
This message was sent by Atlassian Jira
(v8.3.4#803005)