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

OSX build 1 failure:: gsl: gamma.c:1264 #5

Closed
gaming-hacker opened this issue Jan 16, 2016 · 2 comments
Closed

OSX build 1 failure:: gsl: gamma.c:1264 #5

gaming-hacker opened this issue Jan 16, 2016 · 2 comments

Comments

@gaming-hacker
Copy link

i linked this against gfortran-5.3, gfortran-6-latest and gfortran-6-dev with gsl 1.16 all report following

  1 =============================================
  2    fgsl 1.0.0: doc/examples/test-suite.log
  3 =============================================
  4 
  5 # TOTAL: 45
  6 # PASS:  44
  7 # SKIP:  0
  8 # XFAIL: 1
  9 # FAIL:  0
 10 # XPASS: 0
 11 # ERROR: 0
 12 
 13 .. contents:: :depth: 2
 14 
 15 XFAIL: error_1
 16 ==============
 17 
 18 gsl: gamma.c:1264: ERROR: domain error
 19 Default GSL error handler invoked.
 20 
 21 Program received signal SIGABRT: Process abort signal.
 22 
 23 Backtrace for this error:
 24 #0  0x10ce17354
 25 #1  0x10ce16b44
 26 #2  0x7fff8d591ea9
 27 XFAIL error_1 (exit status: 134)
@gaming-hacker gaming-hacker changed the title OSX build 1 failure:: gsl: gamma.c:1264: ERROR OSX build 1 failure:: gsl: gamma.c:1264 Jan 16, 2016
@tschoonj
Copy link
Collaborator

I admit it looks scary but it is actually completely normal and expected 😄

The error_1.f90 example is designed to fail to test the error handling API. This is accomplished here by passing a negative value to fgsl_sf_gamma. This triggers the (default) error handler within GSL (not FGSL), which contains an abort() call resulting in the output you're seeing: the SIGABRT signal is quite revealing here.

The Makefile.am in that directory contains the info needed to run these tests. You will see at the end of the file the following line:

XFAIL_TESTS = error_1

which marks error_1 as a test that is expected to fail. In fact, if for some reason that test would succeed then this would be reported as a failure.

Hope this clears things up a bit!

@gaming-hacker
Copy link
Author

ok thanks!

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

No branches or pull requests

2 participants