Opened 3 years ago

Closed 3 years ago

Last modified 3 years ago

#25482 closed defect (duplicate)

Unhandled segfaults not working properly in Cygwin

Reported by: embray Owned by:
Priority: critical Milestone: sage-duplicate/invalid/wontfix
Component: packages: standard Keywords: cygwin cysignals
Cc: jdemeyer Merged in:
Authors: Reviewers:
Report Upstream: N/A Work issues:
Branch: Commit:
Dependencies: Stopgaps:

Status badges

Description

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 https://github.com/sagemath/cysignals/pull/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.

Change History (5)

comment:1 Changed 3 years ago by embray

  • Keywords cygwin cysignals added

comment:2 Changed 3 years ago by embray

Note: This is fixed by #25814.

comment:3 Changed 3 years ago by vdelecroix

  • Milestone changed from sage-8.3 to sage-8.4

update milestone 8.3 -> 8.4

comment:4 Changed 3 years ago by jdemeyer

  • Milestone changed from sage-8.4 to sage-duplicate/invalid/wontfix
  • Resolution set to duplicate
  • Status changed from new to closed

comment:5 Changed 3 years ago by embray

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.

Note: See TracTickets for help on using tickets.