[SERVER-68070] Jepsen test failures reported as system failures Created: 14/Jul/22 Updated: 19/Jun/23 Resolved: 19/Jun/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Ryan Egesdahl (Inactive) | Assignee: | [DO NOT ASSIGN] Backlog - Server Development Platform Team (SDP) (Inactive) |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | sdp-backlog-purge | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Assigned Teams: |
Server Development Platform
|
||||
| Operating System: | ALL | ||||
| Sprint: | Dev Platform 2022-07-25 | ||||
| Participants: | |||||
| Linked BF Score: | 8 | ||||
| Description |
|
When a server test run in the Jepsen harness, it is currently being reported as a system failure rather than a test failure. This is confusing to anyone investigating a Jepsen variant build failure because it erroneously appears to be related to the Jepsen infrastructure rather than a failing server test. |
| Comments |
| Comment by Alex Neben [ 19/Jun/23 ] |
|
This has been identified as work that the SDP team won't do in the near term. Please reopen with a comment if you feel this work should be reprioritized and explain why. |