From 179f38b18c4152b12ad4eb30683190237dc833bf Mon Sep 17 00:00:00 2001 From: Ross Lawley Date: Mon, 28 Apr 2025 17:10:43 +0100 Subject: [PATCH] Reenable clientside-operations-timeout apply maxAwaitTimeMS if less than remaining timeout test Fixed as part of JAVA-5821 JAVA-5820 --- .../com/mongodb/client/unified/UnifiedTestModifications.java | 4 ---- 1 file changed, 4 deletions(-) diff --git a/driver-sync/src/test/functional/com/mongodb/client/unified/UnifiedTestModifications.java b/driver-sync/src/test/functional/com/mongodb/client/unified/UnifiedTestModifications.java index 2d4d4f49b2..f65845e8df 100644 --- a/driver-sync/src/test/functional/com/mongodb/client/unified/UnifiedTestModifications.java +++ b/driver-sync/src/test/functional/com/mongodb/client/unified/UnifiedTestModifications.java @@ -76,10 +76,6 @@ public static void applyCustomizations(final TestDef def) { .test("client-side-operations-timeout", "timeoutMS behaves correctly for GridFS download operations", "timeoutMS applied to entire download, not individual parts"); - def.skipJira("https://jira.mongodb.org/browse/JAVA-5820") - .test("client-side-operations-timeout", "timeoutMS behaves correctly for tailable awaitData cursors", - "apply maxAwaitTimeMS if less than remaining timeout"); - def.skipJira("https://jira.mongodb.org/browse/JAVA-5815") .test("client-side-operations-timeout", "WaitQueueTimeoutError does not clear the pool", "WaitQueueTimeoutError does not clear the pool");