[SERVER-49705] 'permitted' file may have been deleted by 'after_test' Created: 17/Jul/20  Updated: 29/Oct/23  Resolved: 18/Jan/23

Status: Closed
Project: Core Server
Component/s: Testing Infrastructure
Affects Version/s: None
Fix Version/s: 5.0.15, 6.3.0-rc0, 6.0.5

Type: Bug Priority: Major - P3
Reporter: Vlad Rachev (Inactive) Assignee: Tommaso Tocci
Resolution: Fixed Votes: 0
Labels: neweng, tig-resmoke
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Depends
Assigned Teams:
Server Tooling & Methods
Backwards Compatibility: Fully Compatible
Operating System: ALL
Backport Requested:
v6.2, v6.0, v5.0
Participants:
Linked BF Score: 0

 Description   

See my comment on BF-18211 for details of the bug.

We should change line 339 to use utils.remove_if_exists() to not throw an exception if there is a benign race with after_test().



 Comments   
Comment by Githook User [ 21/Jan/23 ]

Author:

{'name': 'Tommaso Tocci', 'email': 'tommaso.tocci@mongodb.com', 'username': 'toto-dev'}

Message: SERVER-49705 'permitted' file may have been deleted by 'after_test'
Branch: v5.0
https://github.com/mongodb/mongo/commit/458ff3f3ec2b62609492d28d9a618d1dc140b60a

Comment by Githook User [ 20/Jan/23 ]

Author:

{'name': 'Tommaso Tocci', 'email': 'tommaso.tocci@mongodb.com', 'username': 'toto-dev'}

Message: SERVER-49705 'permitted' file may have been deleted by 'after_test'
Branch: v6.0
https://github.com/mongodb/mongo/commit/faf3a3415672ea1935f9f288bf7ecd208a63c5cb

Comment by Githook User [ 18/Jan/23 ]

Author:

{'name': 'Tommaso Tocci', 'email': 'tommaso.tocci@mongodb.com', 'username': 'toto-dev'}

Message: SERVER-49705 'permitted' file may have been deleted by 'after_test'
Branch: master
https://github.com/mongodb/mongo/commit/e3073c252cfce36fb0545a6800443ac3c58dd9f6

Comment by Steven Vannelli [ 10/May/22 ]

Moving this ticket to the Backlog and removing the "Backlog" fixVersion as per our latest policy for using fixVersions.

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