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
Clean up ecl SIGCHLD configuration #15441
Comments
Commit: |
New commits:
|
comment:2
I suspected that this is related to the observed test failure on eno/skynet (#15440) but it is actually not. But its better than what we have so we should ship it. |
comment:3
Haven't been active in sage for a bit. I needed to back off a little bit. I have to agree that looks much nicer and you added a nice looking doctest. |
comment:4
The patch to use ecl_set_option looks good, but the doctest patch looks very wrong : it doesn't check that ECL-in-sage doesn't use SIGCHLD, but rather that SIGCHLD isn't used at all! |
comment:5
I don't understand what you are trying to say. It tests both that neither Sage nor ECL set a SIGCHLD handler, i.e. that it remains NULL. |
Branch pushed to git repo; I updated commit sha1. New commits:
|
comment:7
Is this clearer? |
Changed keywords from none to ecl signal handling sigchld |
comment:8
Looks fine to me. |
Reviewer: Jean-Pierre Flori |
Switch from patching ecl to using
ecl_set_option(ECL_OPT_TRAP_SIGCHLD, 0)
.This ticket was originally a part of #14636.
CC: @SnarkBoojum @jdemeyer @kiwifb
Component: packages: standard
Keywords: ecl signal handling sigchld
Author: Volker Braun, Julien Puydt
Branch/Commit: u/vbraun/ecl_signal_beautification @
7615258
Reviewer: Jean-Pierre Flori
Issue created by migration from https://trac.sagemath.org/ticket/15441
The text was updated successfully, but these errors were encountered: