[SERVER-75632] Enable lockCodeSegmentsInMemory in config fuzzer suites Created: 03/Apr/23 Updated: 21/Jun/23 |
|
| Status: | Backlog |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Jason Chan | Assignee: | Backlog - Service Architecture |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Assigned Teams: |
Service Arch
|
||||||||||||
| Sprint: | Service Arch 2023-04-17, Service Arch 2023-05-01, Service Arch 2023-06-12 | ||||||||||||
| Participants: | |||||||||||||
| Description |
|
Currently, we don't run lockCodeSegmentsInMemory because certain build variants do not have the proper ulimits set. Once set, we should enable the fuzzing. |
| Comments |
| Comment by Jason Chan [ 21/Jun/23 ] |
|
Sending this to backlog since I think this currently has low-value in terms of test coverage, and we should reconsider doing this once |