Build 8.0 beta

[peastman]

Checklist

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

[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.

[peastman]

@conda-forge-admin, please rerender

[peastman]

@conda-forge-admin, please rerender

[peastman]

One build (Linux ARM Pypy Python 3.7) is failing with this message:

SafetyError: The package for pypy3.7 located at /home/conda/feedstock_root/build_artifacts/pkg_cache/pypy3.7-7.3.7-h7cff6a8_2
appears to be corrupted. The path 'bin/pypy3'
has an incorrect size.
  reported size: 6152 bytes
  actual size: 2646 bytes

Any idea what it means?

[jaimergp]

Maybe a temporary problem only? Let's see if retrying fixes it.

[peastman]

I merged the PR, but I don't see any sign of it building the new packages. There's no status indicator at https://github.com/conda-forge/openmm-feedstock/tree/rc, and https://anaconda.org/conda-forge/openmm/files doesn't show any new packages.

[jaimergp]

Try pushing an empty commit directly to rc to kick a retry.

[jakirkham]

Manually started here: https://dev.azure.com/conda-forge/feedstock-builds/_build/results?buildId=534510&view=results

[peastman]

Thanks!

[peastman]

That same build failed again. It's an obscure enough combination (Pypy on ARM Linux) that I won't worry about it for the beta, but we should figure out what's going on. The error message indicates that the pypy3 executable is corrupted.

[jakirkham]

It should be possible to restart the failed builds if it is just an intermittent issue

[peastman]

Since it failed twice in a row, I suspect it's something more than that. The next step would be to test the pypy3.7-7.3.7-h7cff6a8_2 package directly. I don't have access to an ARM Linux system, but maybe it would be possible to create a VM under emulation.

[jakirkham]

If the feedstock is configured to build Linux aarch64 on Azure (and re-rendered), it should be possible to run the build locally using QEMU on x86_64 (Linux). May need to comment out failing bits and add a wait to make sure the Docker container and contents can be investigated

[peastman]

I was thinking of something much simpler than that: just install that pypy package, try to run the executable, and see whether or not it really is broken.