Repository navigation
SB10FD exits whole process on parameter error #126
Description
Activity
A quick search on the internet reveals that various libs override XERBLA not to STOP.
From the netlib docu:
Installers may consider modifying the STOP statement in order to
call system-specific exception-handling facilities.So Travis CI and my OpenSUSE system work fine with the sb10fd unit tests. Apparently not on the Archlinux system I tested this with...
Is this dependent on the LAPACK version used? Which LAPACK does this link to?
openblas 0.3.9 on Archlinux.
libopenblas_pthreads 0.3.9 on OpenSUSE does not exhibit this behavior.
Interestingly Job 387.4 for #129 should fail but does not, because of this bug.
1528$ pytest --pyargs slycot --cov=$slycot_dir --cov-config=../Slycot/.coveragerc 1529============================= test session starts ============================== 1530platform linux -- Python 3.8.1, pytest-5.3.5, py-1.8.0, pluggy-0.13.1 1531rootdir: /home/travis/build/python-control/slycot-coverage 1532plugins: cov-2.8.1 1533collected 107 items 1534 1535tests/test_ab01.py F [ 0%] 1536tests/test_ab08n.py .. [ 2%] 1537tests/test_ag08bd.py .... [ 6%] 1538tests/test_analysis.py ................... [ 24%] 1539tests/test_examples.py ............. [ 36%] 1540tests/test_exceptions.py .. [ 38%] 1541tests/test_mb.py .......... [ 47%] 1542tests/test_mc.py ... [ 50%] 1543tests/test_sb.py ...The command "pytest --pyargs slycot --cov=$slycot_dir --cov-config=../Slycot/.coveragerc" exited with 0.The Travis jobs suffering from this bug use the Netlib reference LAPACK implementation. I wonder if my Archlinux system also uses that despite having compiled against openblas...
In reference to #98 (comment):
The last drop out of the whole Python process should not happen. A simple Exception should be enough. Probably have to patch the Fortran code?