-
Notifications
You must be signed in to change notification settings - Fork 568
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
[PETSc] - Problem with _jll binaries after 3.15.2 #7242
Comments
ai, that is going to be a tricky one to find. It seems to crash in the middle of a computation. |
I believe it just isn't. I may look into it, although we compile our own petsc libraries for all our important runs. However, I've done a couple of tests by manually setting the environment variable and it does not seem to be what causes the crash... |
I doubt that you use multithreaded blas for your local PETSc build. |
You probably want to use |
Hi ! any update on this? |
Not from my side; I'm more than to receive help in compiling new versions of |
Hi all,
I am a developer for GridapPETSc.jl, a package bridging
PETSc_jll
for the Gridap ecosystem.While doing some non-related maintenance, we noticed our tests stopped working for
PETSC_jll
versions above v3.15.2. We also run our tests with manually compiled versions of PETSc, which run fine for all versions up to v3.19.4. Therefore this would point to a bug within the build of the _jll package. Since I am not an expert on artifact building in Julia, I would like some help on the matter.Here is the issue and the PR where I am exploring this matter.
As you can see in the PR, tests run fine for manually compiled PETSc (i.e the CI_EXTRA jobs) but fail for the _jll tests (i.e the CI jobs) which uses the latest
PETSc_jll
v3.18.6. The latter issue is solved if usingPETSc_jll
v3.13.x or v3.15.x instead, and starts failing for newer versions.@boriskaus I understand you have been taking care of most of the releases for
PETSc_jll
(thank you, btw). Would you be able to have a look at this?The text was updated successfully, but these errors were encountered: