-
-
Notifications
You must be signed in to change notification settings - Fork 12.3k
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
cminpack: DIsable blas #183713
cminpack: DIsable blas #183713
Conversation
Else it crashes, see why it has been disabled by default: devernay/cminpack#66 (comment) /cc @chenrui333
How do we reproduce the crash? Also, I don't see any mention of crashes due to BLAS in devernay/cminpack#66. |
@jschueller has a comment about the issue
|
This seems like a build failure and not a crash from using cminpack with BLAS. |
to reproduce the issue just run the full testsuite with DUSE_BLAS=ON you will see that a bunch do fail:
all is ok with DUSE_BLAS=OFF (that is why it is the default since 1.3.9) maybe it could be used instead of embedding a test into the recipe, its very quick to build and run the compilation error you mentioned happened only during the development and should be disregarded |
Test failures seem different from a crash. How do you run the test suite? How long does it take to run? |
they are all segfaults, if I run one manually:
see gdb trace leading to the crash in blas because of incorrect address passed:
|
I tried running the test suite, twice, once with
Are we sure that the tests aren't just broken? |
yes sure, as the gdb stacktrace above |
if you use
you can also try to run this manually |
It will be difficult to run On topic of BLAS, I assume support will need devernay/cminpack@f63e16d. Is it worth trying to get a new release or backporting fixes? |
Rather change the recipe internal test to reflect one of the 10 examples that segfaults like tlmderc: |
hello, |
Else it crashes, see why it has been disabled by default: devernay/cminpack#66 (comment)
I dont have a mac to actually test this but I had the same issue on linux
/cc @chenrui333
HOMEBREW_NO_INSTALL_FROM_API=1 brew install --build-from-source <formula>
, where<formula>
is the name of the formula you're submitting?brew test <formula>
, where<formula>
is the name of the formula you're submitting?brew audit --strict <formula>
(after doingHOMEBREW_NO_INSTALL_FROM_API=1 brew install --build-from-source <formula>
)? If this is a new formula, does it passbrew audit --new <formula>
?