[GODRIVER-924] Test driver on ZAP platforms Created: 03/Apr/19  Updated: 07/Aug/20  Resolved: 07/Aug/20

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

Type: Task Priority: Major - P3
Reporter: Matt Broadstone Assignee: Unassigned
Resolution: Won't Fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
is depended on by TOOLS-1833 Migrate tools (excluding mongoreplay)... Closed
is depended on by DRIVERS-319 Test driver on zSeries, Power and ARM... Closed
Problem/Incident
causes TOOLS-2244 Integration test failures on Ubuntu A... Closed

 Description   

The mongodb tools are experiencing failures on ZAP evergreen builds now that they are ported to the new go driver. Since we need to ship on those platforms, it makes sense that the driver itself should also be tested there. 



 Comments   
Comment by Divjot Arora (Inactive) [ 12/Apr/19 ]

Looking at the patch build linked in TOOLS-2244, the gridfs RoundTrip test fails consistently due to a socket timeout. I tried increasing the timeout at https://github.com/mongodb/mongo-go-driver/blob/master/mongo/gridfs/gridfs_test.go#L202 to 20 seconds and that seemed to work much better (https://evergreen.mongodb.com/version/5cb0cb00d6d80a022fc4c33c).

This issue might be related to https://github.com/golang/go/issues/10775, which was fixed by increasing the timeout for a write test for ARM64 machines.

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