WIP Draft: Validating that mattsu2020 approach to pipes works with all pipe tests #9646
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.
Not for review just for discussion and validation of pipeline handler approach
I took the change that mattsu2020 made to be able to track the pipe signals and just did some messing around to see if that approach could work for all of the pipe related tests. Will use this for inspiration to make PR's for each one individually. I found that some of the original changes didn't work and that the other GNU tests have different expectations for how seq fails