[
https://issues.apache.org/jira/browse/IGNITE-29130?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nikita Amelchev updated IGNITE-29130:
-------------------------------------
Description: The test compares instant thread counts taken from
{{{}/proc{}}}. A joined thread is still listed there for a short while, so
threads of the previous check are counted as the baseline and threads of the
current one as leaked, which makes the test fail under load. [TC
history|https://ci2.ignite.apache.org/test/-4560929016450436238?currentProjectId=IgniteTests24Java8&branch=%3Cdefault%3E].
(was: The test compares instant thread counts taken from {{{}/proc{}}}. A
joined thread is still listed there for a short while, so threads of the
previous check are counted as the baseline and threads of the current one as
leaked, which makes the test fail under load.)
> Fix flaky IgniteClientUserThreadPoolSize test of the C++ thin client
> --------------------------------------------------------------------
>
> Key: IGNITE-29130
> URL: https://issues.apache.org/jira/browse/IGNITE-29130
> Project: Ignite
> Issue Type: Bug
> Reporter: Nikita Amelchev
> Assignee: Nikita Amelchev
> Priority: Minor
> Time Spent: 10m
> Remaining Estimate: 0h
>
> The test compares instant thread counts taken from {{{}/proc{}}}. A joined
> thread is still listed there for a short while, so threads of the previous
> check are counted as the baseline and threads of the current one as leaked,
> which makes the test fail under load. [TC
> history|https://ci2.ignite.apache.org/test/-4560929016450436238?currentProjectId=IgniteTests24Java8&branch=%3Cdefault%3E].
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
