Update recipe (build and testing)

[dalcinl]

Checklist

• Used a fork of the feedstock to propose changes
• Bumped the build number (if the version is unchanged)
• Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)

[conda-forge-linter]

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 (recipe) and found it was in an excellent condition.

[ax3l]

@conda-forge-admin, please rerender

(so we get the fixed conda-build 3.18.7 with conda/conda-build#3596 )

[ax3l]

sorry, still too old in the bot

[minrk]

Pretty sure this will succeed after the aarch64 build finishes. Then happy to have it merged.

[dalcinl]

@minrk Please look at the aarch64 build log, particularly the testing of the openmpi package.

The following NEW packages will be INSTALLED:

    mpi:     1.0-openmpi      conda-forge
    openmpi: 4.0.1-hc99cbb1_2 local      

This smells like dependencies on the C++/Fortran runtime libraries are still broken. Or I am missing something?

Should we just ignore this issue and merge?

I'm tempted to backport the mpivars program from MPICH and install it in $PREFIX/bin, this way we have an actual binary executable that uses MPI, so we can test the core openmpi package. And as a side benefit, the mpivars program is actually useful.

[minrk]

You're right, conda/conda-build#3583 is indeed not fixed in conda-build 3.18.7

[minrk]

We still need to wait for conda-build to fix run_exports before we can make any aarch64 packages. This should put a pause on any/all aarch64 builds across conda-forge, I think.

[ax3l]

@conda-forge-admin, please rerender

(note we are still not using the latest conda-build)

[conda-forge-linter]

Hi! This is the friendly automated conda-forge-webservice.

I tried to re-render for you, but it looks like there was nothing to do.

[conda-forge-linter]

Hi! This is the friendly automated conda-forge-webservice.

I tried to re-render for you, but it looks like there was nothing to do.

[mariusvniekerk]

@minrk Is this right now?

[minrk]

@mariusvniekerk triggering rebuild now to check. The last build was not correct.

[minrk]

@mariusvniekerk No, the build is still incorrect on aarch64, missing strong run_exports from the compilers.

[minrk]

@conda-forge-admin, please rerender

I think the latest CB release may fix this.

[mariusvniekerk]

Fingers crossed

[dalcinl]

@conda-forge-admin, please rerender

[dalcinl]

@beckermr I checked carefully the pkg dependencies of the macOS builds and both look good to me. Could you please double check them and confirm?

PS: I still need to wait for the Linux aarch64 build to check they are OK (we had dependency issues in there).

[beckermr]

LGTM! The aarch64 build will take a while.

[beckermr]

@dalcinl Please close #45 when you merge this.

[beckermr]

huzzah!