[
https://issues.apache.org/jira/browse/IGNITE-20608?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sergey Chugunov updated IGNITE-20608:
-------------------------------------
Description:
Test fails in different branches with timeout in test logic, stack trace:
{code:java}
org.awaitility.core.ConditionTimeoutException: Condition with lambda expression
in org.apache.ignite.internal.runner.app.ItIgniteNodeRestartTest that uses
org.apache.ignite.table.Table, org.apache.ignite.table.Tableint was not
fulfilled within 30 seconds.
at
app//org.awaitility.core.ConditionAwaiter.await(ConditionAwaiter.java:167)
at
app//org.awaitility.core.CallableCondition.await(CallableCondition.java:78)
at
app//org.awaitility.core.CallableCondition.await(CallableCondition.java:26)
at
app//org.awaitility.core.ConditionFactory.until(ConditionFactory.java:985)
at
app//org.awaitility.core.ConditionFactory.until(ConditionFactory.java:954)
at
app//org.apache.ignite.internal.runner.app.ItIgniteNodeRestartTest.checkTableWithData(ItIgniteNodeRestartTest.java:1182)
at
app//org.apache.ignite.internal.runner.app.ItIgniteNodeRestartTest.nodeWithDataTest(ItIgniteNodeRestartTest.java:751)
at
[email protected]/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native
Method)
//... not so important stack trace lines {code}
Its history is available
[here|https://ci.ignite.apache.org/project.html?projectId=ApacheIgnite3xGradle_Test_IntegrationTests&testNameId=7638414685760227643&tab=testDetails],
it is not clear what commit introduced this flakiness.
Some other tests from the same class fail as well, they may share the same root
cause so worth investigating them in the single ticket:
*
[ItIgniteNodeRestartTest.testTwoNodesRestartReverse|https://ci.ignite.apache.org/project.html?projectId=ApacheIgnite3xGradle_Test_IntegrationTests&testNameId=-6899510263921361541&tab=testDetails&branch_ApacheIgnite3xGradle_Test_IntegrationTests=%3Cdefault%3E]
*
[ItIgniteNodeRestartTest.nodeWithDataAndIndexRebuildTest|https://ci.ignite.apache.org/project.html?projectId=ApacheIgnite3xGradle_Test_IntegrationTests&testNameId=6204054563732065266&tab=testDetails&branch_ApacheIgnite3xGradle_Test_IntegrationTests=%3Cdefault%3E]
was:
Test fails in different branches with timeout in test logic, stack trace:
{code:java}
org.awaitility.core.ConditionTimeoutException: Condition with lambda expression
in org.apache.ignite.internal.runner.app.ItIgniteNodeRestartTest that uses
org.apache.ignite.table.Table, org.apache.ignite.table.Tableint was not
fulfilled within 30 seconds.
at
app//org.awaitility.core.ConditionAwaiter.await(ConditionAwaiter.java:167)
at
app//org.awaitility.core.CallableCondition.await(CallableCondition.java:78)
at
app//org.awaitility.core.CallableCondition.await(CallableCondition.java:26)
at
app//org.awaitility.core.ConditionFactory.until(ConditionFactory.java:985)
at
app//org.awaitility.core.ConditionFactory.until(ConditionFactory.java:954)
at
app//org.apache.ignite.internal.runner.app.ItIgniteNodeRestartTest.checkTableWithData(ItIgniteNodeRestartTest.java:1182)
at
app//org.apache.ignite.internal.runner.app.ItIgniteNodeRestartTest.nodeWithDataTest(ItIgniteNodeRestartTest.java:751)
at
[email protected]/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native
Method)
//... not so important stack trace lines {code}
Its history is available
[here|https://ci.ignite.apache.org/project.html?projectId=ApacheIgnite3xGradle_Test_IntegrationTests&testNameId=7638414685760227643&tab=testDetails],
it is not clear what commit introduced this flakiness.
> ItIgniteNodeRestartTest#nodeWithDataTest is flaky on TC
> -------------------------------------------------------
>
> Key: IGNITE-20608
> URL: https://issues.apache.org/jira/browse/IGNITE-20608
> Project: Ignite
> Issue Type: Bug
> Reporter: Sergey Chugunov
> Priority: Major
> Labels: ignite-3
>
> Test fails in different branches with timeout in test logic, stack trace:
> {code:java}
> org.awaitility.core.ConditionTimeoutException: Condition with lambda
> expression in org.apache.ignite.internal.runner.app.ItIgniteNodeRestartTest
> that uses org.apache.ignite.table.Table, org.apache.ignite.table.Tableint was
> not fulfilled within 30 seconds.
> at
> app//org.awaitility.core.ConditionAwaiter.await(ConditionAwaiter.java:167)
> at
> app//org.awaitility.core.CallableCondition.await(CallableCondition.java:78)
> at
> app//org.awaitility.core.CallableCondition.await(CallableCondition.java:26)
> at
> app//org.awaitility.core.ConditionFactory.until(ConditionFactory.java:985)
> at
> app//org.awaitility.core.ConditionFactory.until(ConditionFactory.java:954)
> at
> app//org.apache.ignite.internal.runner.app.ItIgniteNodeRestartTest.checkTableWithData(ItIgniteNodeRestartTest.java:1182)
> at
> app//org.apache.ignite.internal.runner.app.ItIgniteNodeRestartTest.nodeWithDataTest(ItIgniteNodeRestartTest.java:751)
> at
> [email protected]/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native
> Method)
> //... not so important stack trace lines {code}
> Its history is available
> [here|https://ci.ignite.apache.org/project.html?projectId=ApacheIgnite3xGradle_Test_IntegrationTests&testNameId=7638414685760227643&tab=testDetails],
> it is not clear what commit introduced this flakiness.
> Some other tests from the same class fail as well, they may share the same
> root cause so worth investigating them in the single ticket:
> *
> [ItIgniteNodeRestartTest.testTwoNodesRestartReverse|https://ci.ignite.apache.org/project.html?projectId=ApacheIgnite3xGradle_Test_IntegrationTests&testNameId=-6899510263921361541&tab=testDetails&branch_ApacheIgnite3xGradle_Test_IntegrationTests=%3Cdefault%3E]
> *
> [ItIgniteNodeRestartTest.nodeWithDataAndIndexRebuildTest|https://ci.ignite.apache.org/project.html?projectId=ApacheIgnite3xGradle_Test_IntegrationTests&testNameId=6204054563732065266&tab=testDetails&branch_ApacheIgnite3xGradle_Test_IntegrationTests=%3Cdefault%3E]
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
