[SERVER-47771] Error if gdb isn't found on systems that expect it Created: 24/Apr/20 Updated: 06/Dec/22 |
|
| Status: | Backlog |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Raiden Worley (Inactive) | Assignee: | Backlog - Server Tooling and Methods (STM) (Inactive) |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | meta-build-system | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Assigned Teams: |
Server Tooling & Methods
|
||||
| Participants: | |||||
| Linked BF Score: | 55 | ||||
| Story Points: | 2 | ||||
| Description |
|
We check if gdb is present when gathering failed unittests, but don't actually produce any logging output to indicate if it is or error if we are on a system where it should be present but isn't. We have reason to suspect that gdb is occasionally not present when expected, so we should assert it. |
| Comments |
| 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. |