[ 
https://issues.apache.org/jira/browse/IGNITE-25050?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Roman Puchkovskiy updated IGNITE-25050:
---------------------------------------
    Description: 
org.mockito.exceptions.misusing.UnfinishedStubbingException: Unfinished 
stubbing detected here: -> at 
org.apache.ignite.internal.index.ItIndexNodeFinishedRwTransactionsCheckerTest.awaitAddWriteCommittedForAnyMvPartitionStorage(ItIndexNodeFinishedRwTransactionsCheckerTest.java:294)

 

Looks like the problem is that the storage instance to which mock behavior is 
added is null. We should wait for the storage to be created to make sure we 
don't operate with a null storage reference.

  was:
org.mockito.exceptions.misusing.UnfinishedStubbingException: Unfinished 
stubbing detected here: -> at 
org.apache.ignite.internal.index.ItIndexNodeFinishedRwTransactionsCheckerTest.awaitAddWriteCommittedForAnyMvPartitionStorage(ItIndexNodeFinishedRwTransactionsCheckerTest.java:294)

 

Looks like the problem is that the storage instance to which mock behavior is 
added is null. We should not add mock behavior to null storages (they 
correspond to missing partitions).


> ItIndexNodeFinishedRwTransactionsCheckerTest is flaky
> -----------------------------------------------------
>
>                 Key: IGNITE-25050
>                 URL: https://issues.apache.org/jira/browse/IGNITE-25050
>             Project: Ignite
>          Issue Type: Bug
>            Reporter: Roman Puchkovskiy
>            Assignee: Roman Puchkovskiy
>            Priority: Major
>              Labels: ignite-3
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> org.mockito.exceptions.misusing.UnfinishedStubbingException: Unfinished 
> stubbing detected here: -> at 
> org.apache.ignite.internal.index.ItIndexNodeFinishedRwTransactionsCheckerTest.awaitAddWriteCommittedForAnyMvPartitionStorage(ItIndexNodeFinishedRwTransactionsCheckerTest.java:294)
>  
> Looks like the problem is that the storage instance to which mock behavior is 
> added is null. We should wait for the storage to be created to make sure we 
> don't operate with a null storage reference.



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

Reply via email to