DonalEvans commented on a change in pull request #6470:
URL: https://github.com/apache/geode/pull/6470#discussion_r631943224
##########
File path:
geode-core/src/test/java/org/apache/geode/distributed/internal/locks/DLockGrantorTest.java
##########
@@ -18,28 +18,40 @@
import static org.assertj.core.api.Assertions.assertThat;
import static org.assertj.core.api.Assertions.assertThatThrownBy;
import static org.mockito.Mockito.RETURNS_DEEP_STUBS;
+import static org.mockito.Mockito.doNothing;
import static org.mockito.Mockito.doReturn;
+import static org.mockito.Mockito.doThrow;
import static org.mockito.Mockito.mock;
+import static org.mockito.Mockito.never;
import static org.mockito.Mockito.spy;
+import static org.mockito.Mockito.verify;
import static org.mockito.Mockito.when;
import org.junit.Before;
import org.junit.Test;
import org.apache.geode.CancelCriterion;
+import org.apache.geode.cache.CommitConflictException;
import org.apache.geode.cache.TransactionDataNodeHasDepartedException;
import org.apache.geode.distributed.internal.DistributionManager;
import
org.apache.geode.distributed.internal.membership.InternalDistributedMember;
public class DLockGrantorTest {
private DLockService dLockService;
private DLockGrantor grantor;
+ private final DLockBatchId batchId = mock(DLockBatchId.class);
+ private final DLockBatch batch = mock(DLockBatch.class);
+ private final DLockRequestProcessor.DLockRequestMessage request = mock(
+ DLockRequestProcessor.DLockRequestMessage.class);
+ private final InternalDistributedMember owner =
mock(InternalDistributedMember.class);
@Before
public void setup() {
dLockService = mock(DLockService.class, RETURNS_DEEP_STUBS);
DistributionManager distributionManager = mock(DistributionManager.class);
when(dLockService.getDistributionManager()).thenReturn(distributionManager);
+ when(dLockService.getDLockLessorDepartureHandler())
Review comment:
Oh, weird. That must be something to do with how StressNewTest runs
things in parallel.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
