[SERVER-53135] Tassert should only exit with error in testing Created: 30/Nov/20  Updated: 29/Oct/23  Resolved: 18/Dec/20

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 4.9.0

Type: Task Priority: Major - P3
Reporter: Benjamin Caimano (Inactive) Assignee: Tyler Seip (Inactive)
Resolution: Fixed Votes: 0
Labels: servicearch-wfbf-day
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Related
related to SERVER-53380 Improve assert_util classes and imple... Backlog
is related to SERVER-44570 Create a non process-fatal variant of... Closed
Backwards Compatibility: Fully Compatible
Sprint: Service arch 2020-12-28
Participants:

 Description   

During clean shutdown, we check for tripwire assertions and exit uncleanly if they occurred here. We should require that we are doing a clean exit and in testing mode. This means that this behavior will not disrupt customer process control.



 Comments   
Comment by Githook User [ 17/Dec/20 ]

Author:

{'name': 'Tyler Seip', 'email': 'Tyler.Seip@mongodb.com', 'username': 'tseip-mongo'}

Message: SERVER-53135: Make tassert only abort when TestingProctor is enabled
Branch: master
https://github.com/mongodb/mongo/commit/636d1683d510d02df4977b1b7f85457b5980ed1b

Comment by Tyler Seip (Inactive) [ 17/Dec/20 ]

Pre-commit build:

https://spruce.mongodb.com/version/5fdb73270305b97a87101fa2/tasks

All of the failing tests appear to be unrelated to the changes.

Comment by Tyler Seip (Inactive) [ 15/Dec/20 ]

OpenedĀ SERVER-53380 to cover changes requested in the CR not covered by this ticket.

Comment by Tyler Seip (Inactive) [ 10/Dec/20 ]

CR at https://mongodbcr.appspot.com/733250001/

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