-
Notifications
You must be signed in to change notification settings - Fork 214
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
Labels
Comments
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
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
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.
The text was updated successfully, but these errors were encountered: