[SERVER-85343] Evergreen libfuzzer suite should report UBSAN faults as failures Created: 17/Jan/24 Updated: 01/Feb/24 Resolved: 01/Feb/24 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 8.0.0-rc0 |
| Type: | Task | Priority: | Critical - P2 |
| Reporter: | Spencer Jackson | Assignee: | Spencer Jackson |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Server Security
|
| Backwards Compatibility: | Fully Compatible |
| Sprint: | Security 2024-02-05 |
| Participants: |
| Description |
|
libfuzzer tests don't seem to be terminated by UBSAN faults. This was a choice made to allow fuzzers to dig deeper into their entrypoints. However, it makes these tests less deterministic, and makes it harder for Evergreen to interpret their results. |
| Comments |
| Comment by Githook User [ 01/Feb/24 ] |
|
Author: {'name': 'Spencer Jackson', 'email': 'spencer.jackson@mongodb.com', 'username': 'spencerjackson'}Message: GitOrigin-RevId: 7c440dc2b4faab91717dfc333dc88de1542e5d90 |