test(nohup): improve coverage for fd replacement and error paths #8920
+165
−0
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Working on issue #1857 about nohup test coverage.
What's here:
The uncovered lines:
Line 119 (and similar at L110, L124) are
dup2()syscall error paths. These only trigger if the kernel fails to duplicate file descriptors - basically unreachable without fault injection tools. I documented this in the coverage analysis.The remaining uncovered lines are defensive error handling that's realistically untestable in the current test environment. IMO they should stay as-is - better to have defensive code than risk removing safety checks.