[CDRIVER-4341] /Stepdown/not_primary_keep failure Created: 11/Apr/22  Updated: 28/Oct/23  Resolved: 09/Oct/23

Status: Closed
Project: C Driver
Component/s: None
Affects Version/s: None
Fix Version/s: 1.25.0

Type: Task Priority: Major - P3
Reporter: Roberto Sanchez Assignee: Kevin Albertson
Resolution: Fixed Votes: 0
Labels: failing-on-waterfall, flaky-tests
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
is duplicated by CDRIVER-4154 /Stepdown/not_primary_keep fails on c... Closed
Epic Link: Stabilize Evergreen

 Description   

The /Stepdown/not_primary_keep test currently fails and/or is flaky. It produces this error:

Assert Failure: 673 == 674

The test is currently being skipped, so to work on it, it will first be necessary to remove it from .evergreen/skip-tests.txt and run a patch build to determine the current failure mode(s).



 Comments   
Comment by Githook User [ 09/Oct/23 ]

Author:

{'name': 'Kevin Albertson', 'email': 'kevin.albertson@mongodb.com', 'username': 'kevinAlbs'}

Message: CDRIVER-4341 unskip `/Stepdown/not_primary_keep` (#1427)

  • unskip `/Stepdown/not_primary_keep`
  • add reference to specification
  • separate `/Stepdown` tests into `/pooled` and `/single`

This may help to narrow down a test failure. A failing assert does not identify whether a pooled client was used.

Generated at Wed Feb 07 21:20:38 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.