[
https://issues.apache.org/jira/browse/IGNITE-23472?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17892792#comment-17892792
]
Ignite TC Bot commented on IGNITE-23472:
----------------------------------------
{panel:title=Branch: [pull/11615/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/11615/head] Base: [master] : No new tests
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}{panel}
[TeamCity *--> Run :: All*
Results|https://ci2.ignite.apache.org/viewLog.html?buildId=8127365&buildTypeId=IgniteTests24Java8_RunAll]
> Fix flaky JavaLoggerTest
> ------------------------
>
> Key: IGNITE-23472
> URL: https://issues.apache.org/jira/browse/IGNITE-23472
> Project: Ignite
> Issue Type: Bug
> Reporter: Maksim Timonin
> Assignee: Aleksandr Chesnokov
> Priority: Minor
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Field `JavaLogger#inited` is used for DCL pattern while initializing logger.
> The test checks `JavaLogger#cfg` to be non-null that is actually null if run
> test multiple times. There is no guarantee for the `cfg` field to be
> initialized with the DCL.
> Need to investigate how to refactor JavaLogger to make test green.
>
> [https://ci2.ignite.apache.org/buildConfiguration/IgniteTests24Java8_RunAll/8117150?buildTab=tests&suite=org.apache.ignite.testsuites.IgniteLoggingSelfTestSuite%3A+&package=org.apache.ignite.logger.java&class=JavaLoggerTest]
--
This message was sent by Atlassian Jira
(v8.20.10#820010)