Ivan Zlenko created IGNITE-27165:
------------------------------------
Summary:
ThrottlingTest.wakeupSpeedBaseThrottledThreadOnCheckpointFinish became flaky
Key: IGNITE-27165
URL: https://issues.apache.org/jira/browse/IGNITE-27165
Project: Ignite
Issue Type: Bug
Reporter: Ivan Zlenko
Sometimes ThrottlingTest.wakeupSpeedBaseThrottledThreadOnCheckpointFinish start
to fail with the following reason:
{code:java}
org.opentest4j.AssertionFailedError: load-0 ==> expected: <true> but was:
<false>
at
app//org.junit.jupiter.api.AssertionFailureBuilder.build(AssertionFailureBuilder.java:151)
at
app//org.junit.jupiter.api.AssertionFailureBuilder.buildAndThrow(AssertionFailureBuilder.java:132)
at app//org.junit.jupiter.api.AssertTrue.failNotTrue(AssertTrue.java:63)
at app//org.junit.jupiter.api.AssertTrue.assertTrue(AssertTrue.java:36)
at app//org.junit.jupiter.api.Assertions.assertTrue(Assertions.java:214)
at
app//org.apache.ignite.internal.pagememory.persistence.throttling.ThrottlingTest.wakeupSpeedBaseThrottledThreadOnCheckpointFinish(ThrottlingTest.java:266)
{code}
Potentially raising timeout could help, also it will be a good to migrate from
waitForCondition to awaitility so it will be clear what condition was not met.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
