-
-
Notifications
You must be signed in to change notification settings - Fork 3
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
Libscotch7.0.5 #5
Conversation
…nda-forge-pinning 2024.09.26.07.35.45
Hi! This is the friendly automated conda-forge-linting service. I just wanted to let you know that I linted all conda-recipes in your PR ( |
…nda-forge-pinning 2024.09.26.07.35.45
@conda-forge-admin, please rerender |
…nda-forge-pinning 2024.11.17.06.32.00
Hi! This is the friendly automated conda-forge-linting service. I was trying to look for recipes to lint for you, but it appears we have a merge conflict. Please try to merge or rebase with the base branch to resolve this conflict. Please ping the 'conda-forge/core' team (using the @ notation in a comment) if you believe this is a bug. |
@conda-forge-admin, please rerender |
Hi! This is the friendly automated conda-forge-linting service. I just wanted to let you know that I linted all conda-recipes in your PR ( |
…nda-forge-pinning 2024.11.18.09.20.23
@Kabbone sry for pinging you here but I do not know how to debug the test errors. Maybe you have an idea. |
you build scotch INT32 and PaStiX is default INT64, if you want INT32 you need to pass a build flag "PASTIX_INT64=OFF" |
Thanks foryour response @Kabbone. I think the scotch builds have int64 support. Also this feedstock seems to build fine. What is failing now are the ctests. |
You see in the build of pastix that scotch 8 Byte test of cmake is failing and 4 Byte successful. Or did I look at the wrong build?
…On November 18, 2024 10:58:15 PM GMT+01:00, lorenz ***@***.***> wrote:
Thanks foryour response @Kabbone. I think the scotch builds have int64 support. Also this feedstock seems to build fine. What is failing now are the ctests.
--
Reply to this email directly or view it on GitHub:
#5 (comment)
You are receiving this because you were mentioned.
Message ID: ***@***.***>
|
Ah thanks, yes true, so it's still the same issue. |
Hi! This is the friendly automated conda-forge-linting service. I just wanted to let you know that I linted all conda-recipes in your PR ( I do have some suggestions for making it better though... For recipe/meta.yaml:
This message was generated by GitHub Actions workflow run https://github.com/conda-forge/conda-forge-webservices/actions/runs/12097517658. Examine the logs at this URL for more detail. |
…onda-forge-pinning 2024.11.30.12.23.39
Checklist
0
(if the version changed)conda-smithy
(Use the phrase@conda-forge-admin, please rerender
in a comment in this PR for automated rerendering)