[SERVER-1125] Make a slow test to run all sharding tests through valgrind Created: 16/May/10  Updated: 30/Jan/18  Resolved: 30/Jan/18

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

Type: New Feature Priority: Major - P3
Reporter: Mathias Stearn Assignee: DO NOT USE - Backlog - Test Infrastructure Group (TIG)
Resolution: Won't Fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Participants:

 Description   

Need to call _exit for these tests to avoid all the issues that are flagged at shutdown due to incorrect global semantics.



 Comments   
Comment by Max Hirschhorn [ 30/Jan/18 ]

redbeard0531, acm, has this request effectively been satisfied by integrating ASan and UBSan into Evergreen? Are there other checks we'd get out of valgrind that we don't have with our current sanitizers?

Comment by Eric Milkie [ 29/Feb/12 ]

might be able to do this with discretionary use of _exit

Comment by Mathias Stearn [ 14/Jun/10 ]

Added --useValgrind=1 option to the simple-setup.py sharding script. No good way to run automatically in a test case.

Comment by auto [ 25/May/10 ]

Author:

{'login': 'RedBeard0531', 'name': 'Mathias Stearn', 'email': 'mathias@10gen.com'}

Message: Start of work on valgrind test for mongos SERVER-1125
http://github.com/mongodb/mongo/commit/560b7baafc3183ededabe99a65510ee1f39ac385

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