[SERVER-64999] Disable, rehabilitate, and re-enable sanitizer builds under icecream Created: 28/Mar/22 Updated: 29/Oct/23 Resolved: 05/Apr/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 5.3.2 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Andrew Morrow (Inactive) | Assignee: | Daniel Moody |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||||||
| Sprint: | Dev Platform 2022-04-18 | ||||||||||||||||||||
| Participants: | |||||||||||||||||||||
| Description |
|
We have reason to believe, per investigations done while pursuing In order to prevent developers from getting false positive results, we should first make a commit to prevent that combination. Then we should get the feature working again and remove the guard rails. Per daniel.moody, one intriguing idea about how to solve the issue permanently is to see if we can just always make the files that are named in the suppression files build locally, by digging the relevant paths out of the suppression files. |
| Comments |
| Comment by Githook User [ 04/Apr/22 ] |
|
Author: {'name': 'Daniel Moody', 'email': 'daniel.moody@mongodb.com', 'username': 'dmoody256'}Message: |
| Comment by Iryna Zhuravlova [ 04/Apr/22 ] |
|
We are going the first part of the ticket and then reassess how to proceed with the rest |