[GODRIVER-1205] Fix bug in transaction tests on 4.3 evergreen Created: 25/Jul/19  Updated: 27/Oct/23  Resolved: 30/Sep/19

Status: Closed
Project: Go Driver
Component/s: CRUD
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Emmanuel Eppinger (Inactive) Assignee: Unassigned
Resolution: Gone away Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Gantt Dependency
has to be done after GODRIVER-624 Retryable Reads Closed
Epic Link: Robust Testing Framework

 Description   

So as per offline discussion the file has been renamed to remove the z_ but that makes tests fail on evergreen. Figure out what is going on there and what 4.3 is and why the tests are failing there.

 

Old stuff:

naming retryable_reads_test.go (without the z_) causes transaction tests to fail on 4.3 on evergreen. It looks like the nth test fails on evergreen because the collection becomes empty for somereason. If this is a test is a spec test with an outcome, the collection is empty so the outcome is wrong. Renaming the retryable reads test to start with z_ was a work around that moved the issue to fall on a test without an outcome.

 

Evergreen patch with workaround: https://evergreen.mongodb.com/version/5d39dd989ccd4e52a4fbd4df

 

Evergreen patch with issue and differently ordered tests to show that its not a particular test that is failing but the nth test in the mongo package to be affected by this issue: https://evergreen.mongodb.com/version/5d38c61a3627e01527323b06

 

Evergreen patch with the issue and normally ordered tests: https://evergreen.mongodb.com/version/5d386cf91e2d171348bc2f34



 Comments   
Comment by Divjot Arora (Inactive) [ 30/Sep/19 ]

I checked some variants and the only tests failing on the latest server version are index-related, so I'm closing this ticket.

Generated at Thu Feb 08 08:35:54 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.