-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
env: fix regression of --ignore-signal=PIPE
#9618
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
|
GNU testsuite comparison: |
c362cfb to
62e4f7b
Compare
|
GNU testsuite comparison: |
62e4f7b to
67a4741
Compare
|
GNU testsuite comparison: |
67a4741 to
8a264a0
Compare
|
GNU testsuite comparison: |
8a264a0 to
73a0844
Compare
|
GNU testsuite comparison: |
|
please fix the conflicts |
73a0844 to
98e348d
Compare
I have fixed the conflicts. However while doing it I have noticed that the test fails if the default "yes" is from uutils coreutils on the machine running the test (it works with "yes" from GNU coreutils). This is because uutils yes unconditionally restores the sigpipe handler to its default value (by calling I could fix it in this PR as well, but it is not directly related in principle. |
|
GNU testsuite comparison: |
- revert uutils#9614 because `Command::exec()` resets the default signal handler for SIGPIPE, interfering with the option `--ignore-signal=PIPE` - add regression-test for --ignore-signal=PIPE - add FIXME comment about execvp() Signed-off-by: Etienne Cordonnier <ecordonnier@snap.com>
98e348d to
cffd508
Compare
|
GNU testsuite comparison: |
Command::exec()resets the default signal handler for SIGPIPE, interfering with the option--ignore-signal=PIPEFixes #9617