Skip to content
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

Unhandled segfaults not working properly in Cygwin #25482

Closed
embray opened this issue May 31, 2018 · 4 comments
Closed

Unhandled segfaults not working properly in Cygwin #25482

embray opened this issue May 31, 2018 · 4 comments

Comments

@embray
Copy link
Contributor

embray commented May 31, 2018

For example, the following test fails:

sage -t src/sage/parallel/decorate.py
**********************************************************************
File "src/sage/parallel/decorate.py", line 564, in sage.parallel.decorate.fork
Failed example:
    print("this works"); g()
Expected:
    this works...
    <BLANKLINE>
    ------------------------------------------------------------------------
    Unhandled SIG...
    ------------------------------------------------------------------------
    'NO DATA'
Got:
    this works
    ------------------------------------------------------------------------
    'NO DATA'
**********************************************************************
1 item had failures:
   1 of  18 in sage.parallel.decorate.fork
    [90 tests, 1 failure, 31.67 s]

This is due to sagemath/cysignals#83 which is fixed in Cysignals. I tested that an update Cysignals fixed the test. So we just need to make sure to release a new Cysignals and update Sage to it for 8.3.

CC: @jdemeyer

Component: packages: standard

Keywords: cygwin cysignals

Issue created by migration from https://trac.sagemath.org/ticket/25482

@embray embray added this to the sage-8.3 milestone May 31, 2018
@embray
Copy link
Contributor Author

embray commented Jul 7, 2018

Changed keywords from none to cygwin cysignals

@embray
Copy link
Contributor Author

embray commented Jul 18, 2018

comment:2

Note: This is fixed by #25814.

@videlec
Copy link
Contributor

videlec commented Aug 3, 2018

comment:3

update milestone 8.3 -> 8.4

@videlec videlec modified the milestones: sage-8.3, sage-8.4 Aug 3, 2018
@jdemeyer jdemeyer removed this from the sage-8.4 milestone Aug 3, 2018
@jdemeyer jdemeyer closed this as completed Aug 3, 2018
@embray
Copy link
Contributor Author

embray commented Aug 6, 2018

comment:5

I wouldn't really consider this a duplicate. This issue is not identical with the fix in this case. But whatever, it's not too important.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants