[SERVER-57755] More aggressively fail tests where a node unexpectedly crashes instead of timing out Created: 16/Jun/21 Updated: 05/Feb/24 Resolved: 05/Feb/24 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Testing Infrastructure |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Daniel Gottlieb (Inactive) | Assignee: | [DO NOT ASSIGN] Backlog - DevProd Correctness |
| Resolution: | Won't Do | Votes: | 1 |
| Labels: | tig-resmoke | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Assigned Teams: |
Correctness
|
||||
| Participants: | |||||
| Linked BF Score: | 165 | ||||
| Description |
|
I assume this depends more on which kinds of tests are being run, but it's relatively common for a node crashing to result in the test coming to a halt and timing out instead of failing. Major benefits:
Apologies if this ticket already exists – I felt I had seen one before. I was struggling to come up with the right keywords to find it. |
| Comments |
| Comment by Thomas Langston [ 05/Feb/24 ] |
|
It appears this issue has been resolved by other changes in another Epic. Please open a new issue if this issue reappears. |
| Comment by Steven Vannelli [ 10/May/22 ] |
|
Moving this ticket to the Backlog and removing the "Backlog" fixVersion as per our latest policy for using fixVersions. |