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

Fix test_fpe and test_mark_point for Cygwin #97

Open
brarcher opened this issue Dec 19, 2016 · 0 comments
Open

Fix test_fpe and test_mark_point for Cygwin #97

brarcher opened this issue Dec 19, 2016 · 0 comments

Comments

@brarcher
Copy link
Contributor

brarcher commented Dec 19, 2016

The test_fpe and test_mark_point tests currently fail on Cygwin. Instead of the test process receiving a SIGFPE it instead fails with a SIGSEGV. The reason is not yet know. However, attempting a simple program that installs a SIGFPE handler then does a raise(SIGFPE) does result in the handler being called.

When this issue is resolved the unit tests need to be enabled for Cygwin on AppVeyor.

brarcher added a commit that referenced this issue Dec 19, 2016
The test_fpe test currently fails on Cygwin. Instead of the test
process receiving a SIGFPE it instead fails with a SIGSEGV. The
reason is not yet know. However, attempting a simple program
that installs a SIGFPE handler then does a raise(SIGFPE) does
result in the handler being called.

This test needs to be enabled again once the reason for the failure
is resolved.

See: #97
brarcher added a commit that referenced this issue Dec 19, 2016
The test_fpe test currently fails on Cygwin. Instead of the test
process receiving a SIGFPE it instead fails with a SIGSEGV. The
reason is not yet know. However, attempting a simple program
that installs a SIGFPE handler then does a raise(SIGFPE) does
result in the handler being called.

This test needs to be enabled again once the reason for the failure
is resolved.

See: #97
@brarcher brarcher changed the title Fix test_fpe for Cygwin Fix test_fpe and test_mark_point for Cygwin Dec 19, 2016
brarcher added a commit that referenced this issue Dec 19, 2016
The test_fpe and test_mark_point tests currently fail on Cygwin.
Instead of the test process receiving a SIGFPE it instead fails
with a SIGSEGV. The reason is not yet know. However, attempting a
simple program that installs a SIGFPE handler then does a
raise(SIGFPE) does result in the handler being called.

This tests need to be enabled again once the reason for the failures
is resolved.

See: #97
brarcher added a commit that referenced this issue Dec 23, 2016
The test_fpe and test_mark_point tests currently fail on Cygwin.
Instead of the test process receiving a SIGFPE it instead fails
with a SIGSEGV. The reason is not yet know. However, attempting a
simple program that installs a SIGFPE handler then does a
raise(SIGFPE) does result in the handler being called.

This tests need to be enabled again once the reason for the failures
is resolved.

#97
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

1 participant