You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ignite.apache.org by "Ignite TC Bot (Jira)" <ji...@apache.org> on 2022/10/11 06:57:00 UTC

[jira] [Commented] (IGNITE-17863) ThreadNameValidationTest fails if run alone (or first in suite)

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

Ignite TC Bot commented on IGNITE-17863:
----------------------------------------

{panel:title=Branch: [pull/10301/head] Base: [master] : Possible Blockers (1)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Cache 2{color} [[tests 0 TIMEOUT , Out Of Memory Error , Exit Code |https://ci.ignite.apache.org/viewLog.html?buildId=6824155]]

{panel}
{panel:title=Branch: [pull/10301/head] Base: [master] : No new tests found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}{panel}
[TeamCity *--&gt; Run :: All* Results|https://ci.ignite.apache.org/viewLog.html?buildId=6823275&amp;buildTypeId=IgniteTests24Java8_RunAll]

> ThreadNameValidationTest fails if run alone (or first in suite)
> ---------------------------------------------------------------
>
>                 Key: IGNITE-17863
>                 URL: https://issues.apache.org/jira/browse/IGNITE-17863
>             Project: Ignite
>          Issue Type: Bug
>            Reporter: Roman Puchkovskiy
>            Assignee: Roman Puchkovskiy
>            Priority: Major
>              Labels: MakeTeamcityGreenAgain
>             Fix For: 2.15
>
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> This seems to happen because code that configures Log4j logging system triggers creation of a thread factory after the test saves the count of created thread factories, so the test thinks that there is some production code doing so, even though it's an artifact of our test code.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)