[SERVER-50362] Add resilience to repeat execution for multiversion tag generation Created: 18/Aug/20  Updated: 29/Oct/23  Resolved: 19/Aug/20

Status: Closed
Project: Core Server
Component/s: Testing Infrastructure
Affects Version/s: None
Fix Version/s: 4.4.1, 4.7.0

Type: Bug Priority: Major - P3
Reporter: Raiden Worley (Inactive) Assignee: Raiden Worley (Inactive)
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Backwards Compatibility: Fully Compatible
Operating System: ALL
Backport Requested:
v4.4
Sprint: STM 2020-08-24
Participants:
Story Points: 1

 Description   

If a task likeĀ sharding_multiversion_gen is run more than once, the generated_resmoke_config directory isn't created, so placing a tag file in it fails.

It should be relatively safe to no-op if the path we're placing the tag file in doesn't exist; if this happens when it shouldn't then in the worst case a test will run which should've been excluded and fail, which would let us know something was wrong.



 Comments   
Comment by Githook User [ 19/Aug/20 ]

Author:

{'name': 'Carl Raiden Worley', 'email': 'carl.worley@10gen.com', 'username': 'aggrand'}

Message: SERVER-50362 Add resilience to repeat execution for multiversion tag generation
Branch: v4.4
https://github.com/mongodb/mongo/commit/f63a0a4204266c661e87ce704d91ade9511f1fd5

Comment by Githook User [ 19/Aug/20 ]

Author:

{'name': 'Carl Raiden Worley', 'email': 'carl.worley@10gen.com', 'username': 'aggrand'}

Message: SERVER-50362 Add resilience to repeat execution for multiversion tag generation
Branch: master
https://github.com/mongodb/mongo/commit/2ead81e671ef4083217f9a894f76a2f95d7415ff

Generated at Thu Feb 08 05:22:28 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.