You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Alexey Goncharuk (JIRA)" <ji...@apache.org> on 2018/03/01 15:16:00 UTC
[jira] [Commented] (IGNITE-6557) Test
IgniteTxRemoveTimeoutObjectsTest has flaky fails
[ https://issues.apache.org/jira/browse/IGNITE-6557?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16382129#comment-16382129 ]
Alexey Goncharuk commented on IGNITE-6557:
------------------------------------------
Hi [~VitaliyB],
Can you please replace sleep() with GridTestUtils.waitForCondition(<check predicate>, getTestTimeout()) and then assert that wait returned true? The sleep() is quite unreliable and sensitive to timeout processor changes.
> Test IgniteTxRemoveTimeoutObjectsTest has flaky fails
> -----------------------------------------------------
>
> Key: IGNITE-6557
> URL: https://issues.apache.org/jira/browse/IGNITE-6557
> Project: Ignite
> Issue Type: Bug
> Affects Versions: 2.2
> Reporter: Vitaliy Biryukov
> Assignee: Vitaliy Biryukov
> Priority: Major
> Labels: MakeTeamcityGreenAgain
> Fix For: 2.5
>
>
> Build log:
> {noformat}
> [org.apache.ignite.internal.processors.cache.distributed.IgniteTxRemoveTimeoutObjectsTest.testTxRemoveTimeoutObjects] junit.framework.AssertionFailedError: Grids contain LockTimeoutObjects.
> at junit.framework.Assert.fail(Assert.java:57)
> at junit.framework.TestCase.fail(TestCase.java:227)
> at org.apache.ignite.internal.processors.cache.distributed.IgniteTxRemoveTimeoutObjectsTest.assertDoesNotContainLockTimeoutObjects(IgniteTxRemoveTimeoutObjectsTest.java:135)
> at org.apache.ignite.internal.processors.cache.distributed.IgniteTxRemoveTimeoutObjectsTest.testTxRemoveTimeoutObjects(IgniteTxRemoveTimeoutObjectsTest.java:92)
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)