[
https://issues.apache.org/jira/browse/IGNITE-12663?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17035556#comment-17035556
]
Andrey N. Gura edited comment on IGNITE-12663 at 2/12/20 5:58 PM:
------------------------------------------------------------------
[~ilyak] From my point this restriction will lead to:
- many unexpected failed and frozen tests
- starvations
- impossibility to detect some races
I really don't like this idea.
You always can cut off thread dumps from the log (at least partially).
was (Author: agura):
[~ilyak] What is your motivation? From my point this restriction will lead to:
- many unexpected failed and frozen tests
- starvations
- impossibility to detect some races
I really don't like this idea.
> Let's limit all thread pools' sizes to 3 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
>
> The rationale is, it is very painful shoving through thread dumps of test
> with N CPU threads in every pool.
> Why 3? It should allow all kinds of race conditions to still happen. Of
> course, we should allow specific tests to override this value.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
