[SERVER-31095] Add builder to validate continued correctness of the legacy TransportLayer Created: 14/Sep/17  Updated: 30/Oct/23  Resolved: 22/Sep/17

Status: Closed
Project: Core Server
Component/s: Networking
Affects Version/s: None
Fix Version/s: 3.6.0-rc0

Type: Task Priority: Major - P3
Reporter: Andrew Morrow (Inactive) Assignee: Henrik Edin
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Backwards Compatibility: Fully Compatible
Sprint: Platforms 2017-10-02
Participants:

 Description   

We currently default to the ASIO TransportLayer, but we intend to ship the Legacy TransportLayer as an available fallback (before we remove it in 3.8). Since we will still be making it available, we should ensure that it does not regress.

Add copies of the two "async" builders and set them to run with the legacy TL.



 Comments   
Comment by Githook User [ 22/Sep/17 ]

Author:

{'email': 'henrik.edin@mongodb.com', 'name': 'Henrik Edin', 'username': 'henrikedin'}

Message: SERVER-31095 Adding an evergreen builder to test the legacy transport layer. Fix so resmoke.py can passthrough the --transportLayer option.
Branch: master
https://github.com/mongodb/mongo/commit/c79b69d1ead95ba93e33ea4e1859119752d42f7f

Generated at Thu Feb 08 04:25:59 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.