[
https://issues.apache.org/jira/browse/IGNITE-20343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17766301#comment-17766301
]
Vadim Pakhnushev commented on IGNITE-20343:
-------------------------------------------
Root cause of this is a race condition in the config file implementation, where
several worker threads try to get or create a section name, and unlucky thread
gets an exception and doesn't update the values from the server.
> Flaky ItIgnitePicocliCommandsTest
> ---------------------------------
>
> Key: IGNITE-20343
> URL: https://issues.apache.org/jira/browse/IGNITE-20343
> Project: Ignite
> Issue Type: Bug
> Components: cli
> Affects Versions: 3.0.0-beta1
> Reporter: Dmitry Baranov
> Assignee: Vadim Pakhnushev
> Priority: Major
> Labels: ignite-3
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Failure example
> [test
> result|https://ci.ignite.apache.org/buildConfiguration/ApacheIgnite3xGradle_Test_IntegrationTests_ModuleCli/7475403?hideProblemsFromDependencies=false&hideTestsFromDependencies=false&expandBuildProblemsSection=true&expandBuildTestsSection=true&expandBuildChangesSection=true]
>
> {code:java}
> org.awaitility.core.ConditionTimeoutException: Lambda expression in
> org.apache.ignite.internal.cli.core.repl.executor.ItIgnitePicocliCommandsTest:
> expected not an empty collection but was <[]> within 10 seconds. at
> app//org.awaitility.core.ConditionAwaiter.await(ConditionAwaiter.java:167)
> at
> app//org.awaitility.core.AbstractHamcrestCondition.await(AbstractHamcrestCondition.java:86)
> at
> app//org.awaitility.core.ConditionFactory.until(ConditionFactory.java:985)
> at
> app//org.awaitility.core.ConditionFactory.until(ConditionFactory.java:691)
> at
> app//org.apache.ignite.internal.cli.core.repl.executor.ItIgnitePicocliCommandsTest.nodeNameSuggested(ItIgnitePicocliCommandsTest.java:350)
> {code}
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
