env: add --default-signal, --block-signal, and --list-signal-handling options #9658
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
ChrisDryden
force-pushed
the
env_signal_options
branch
2 times, most recently
from
8670fcc to
d34a4de
Compare
Collaborator
Author
|
Let me know if you'd rather I'd split this into three different PR's for each of the three options? |
|
GNU testsuite comparison: |
ChrisDryden
force-pushed
the
env_signal_options
branch
from
d34a4de to
c2d6134
Compare
|
GNU testsuite comparison: |
Collaborator
Author
|
The two failing builds are just being flaky |
This was referenced Dec 15, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Now that there's a mechanism for us to read the pipeline signals, I wanted to get started on the ability to add that capability to env for better testing. #9657 this is the PR that implements the macro in signal handling that allows for reading the pipeline signals.
With these two PR's combined the gnu env signal test passes. I want to add more integration tests in here but I need to wait until the pipeline signal reader macro is in some of our utilities to be able to use our utilities in the testing to validate that it matches the expectations in the GNU tests.