[SERVER-8337] Failpoints should be able to be configured to set errno to a given value when triggered Created: 25/Jan/13 Updated: 23/Feb/23 Resolved: 24/Feb/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Testing Infrastructure |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Minor - P4 |
| Reporter: | Andrew Morrow (Inactive) | Assignee: | Backlog - Service Architecture |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | devtools-to-servicearch, re-triaged-ticket | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Assigned Teams: |
Service Arch
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Participants: | |||||
| Description |
|
Failpoints are often injected at system call sites (send/recv). Typically the error-occurred branch of the nearby code for system calls will examine 'errno' and respond to that value in some way (often by capturing it in an exception). If, however, the error-occurred branch is taken because the failpoint is enabled, rather than because the syscall failed, then the value of errno is indeterminate, and therefore the path through the error handling logic cannot be controlled. The failpoints mechanism should offer a facility to associate an errno value with an activated failpoint, so that when the failpoint triggers errno is set to the stored value. This would make it possible to control the behavior of the error-occurred branch when the failpoint is active. |
| Comments |
| Comment by Blake Oler [ 27/Oct/22 ] |
|
Keeping closed, this functionality can be implemented inside the body of specific failpoints if needed. |
| Comment by Lauren Lewis (Inactive) [ 24/Feb/22 ] |
|
We haven’t heard back from you for at least one calendar year, so this issue is being closed. If this is still an issue for you, please provide additional information and we will reopen the ticket. |