Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Update cursors to refresh timeoutMS on close without affecting the timeout of the operation #1527

Open
wants to merge 2 commits into
base: main
Choose a base branch
from
Open

Update cursors to refresh timeoutMS on close without affecting the timeout of the operation #1527

wants to merge 2 commits into from

Conversation

stIncMale
Copy link
Member

@stIncMale stIncMale self-assigned this Oct 8, 2024
stIncMale
stIncMale commented Oct 8, 2024
View reviewed changes
driver-core/src/test/functional/com/mongodb/internal/operation/AsyncCommandBatchCursorTest.java
@@ -86,7 +90,7 @@ void setUp() {

connectionSource = mock(AsyncConnectionSource.class);
operationContext = mock(OperationContext.class);
timeoutContext = mock(TimeoutContext.class);
timeoutContext = new TimeoutContext(TimeoutSettings.create(MongoClientSettings.builder().timeout(3, TimeUnit.SECONDS).build()));
Copy link
Member Author

@stIncMale stIncMale Oct 8, 2024 •
edited
Loading

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I had to get rid of unnecessary mocking here and in other places to make the tests pass with the new code in cursors.

@stIncMale
Copy link
Member Author

stIncMale commented Oct 9, 2024 •
edited
Loading

Given how flaky our tests are, it is difficult to tell whether the failures in the PR are caused by the PR, or they've been in the main branch, and Evergreen provides no tools to facilitate searching for an answer even for a single test failure. So I had to search manually, and try running tests from the main branch. Following are the result.

Failures that don't seem to be new:

  1. Load Balancer 8.0 Auth SSL JDK21 Ubuntu: com.mongodb.reactivestreams.client.unified.LoadBalancerTest.cursors_are_correctly_pinned_to_connections_for_load-balanced_clusters__pinned_connections_are_returned_after_a_network_error_during_a_killCursors_request (happened in main here)
  2. 4.2 Sharded Cluster NoAuth NoSSL JDK8 Linux: com.mongodb.client.ServerSelectionProseTest.operationCountBasedSelectionWithinLatencyWindow__ (happened in main, see here)
  3. 7.0 Replica Set Auth SSL JDK8 Linux: com.mongodb.reactivestreams.client.ClientSideOperationTimeoutProseTest.6._GridFS_Download (reproduced against main here)

Failures that may be new (I failed to manually find such failures in main, but my search was quite limited):

  1. 6.0 Sharded Cluster NoAuth NoSSL JDK8 Linux: com.mongodb.client.unified.ClientSideEncryptionTest.namedKMS-rewrapManyDataKey__rewrap_to_azure_name1
  2. the same test as in #2 5.0 Replica Set NoAuth NoSSL JDK8 Linux: com.mongodb.client.unified.ClientSideEncryptionTest.namedKMS-rewrapManyDataKey__rewrap_to_kmip_name1

When I re-run the later ones here, both succeeded.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@vbabanin vbabanin Awaiting requested review from vbabanin

Assignees

@stIncMale stIncMale

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
1 participant
@stIncMale