You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ignite.apache.org by "Roman Puchkovskiy (Jira)" <ji...@apache.org> on 2024/03/19 13:48:00 UTC

[jira] [Commented] (IGNITE-21764) PersistentPageMemoryMvTableStorageTest.testIndexDestructionOnRecovery is flaky

    [ https://issues.apache.org/jira/browse/IGNITE-21764?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17828346#comment-17828346 ] 

Roman Puchkovskiy commented on IGNITE-21764:
--------------------------------------------

The patch looks good to me

> PersistentPageMemoryMvTableStorageTest.testIndexDestructionOnRecovery is flaky
> ------------------------------------------------------------------------------
>
>                 Key: IGNITE-21764
>                 URL: https://issues.apache.org/jira/browse/IGNITE-21764
>             Project: Ignite
>          Issue Type: Bug
>            Reporter: Aleksandr Polovtcev
>            Assignee: Aleksandr Polovtcev
>            Priority: Blocker
>              Labels: ignite-3
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> A failure can be found here: https://ci.ignite.apache.org/buildConfiguration/ApacheIgnite3xGradle_Test_RunAllTests/7936530
> There's a race between destroying and creating an index, I believe this is a test problem, because we shouldn't have identical index IDs in such situations in real life.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)