Aarch builds corrupted?

conda-forge / pypy3.6-feedstock

A conda-smithy repository for pypy3.6.

BSD 3-Clause "New" or "Revised" License

4 stars 13 forks source link

Aarch builds corrupted? #83

Closed h-vetinari closed 2 years ago

h-vetinari commented 2 years ago

The following is appearing in https://github.com/conda-forge/numpy-feedstock/pull/272, even after a restart:

SafetyError: The package for pypy3.8 located at /home/conda/feedstock_root/build_artifacts/pkg_cache/pypy3.8-7.3.9-hfb6fae5_1
appears to be corrupted. The path 'bin/pypy3'
has an incorrect size.
  reported size: 6192 bytes
  actual size: 2639 bytes

h-vetinari commented 2 years ago

Which is surprising, because there hasn't been any (visible) change in the artefacts.

xhochy commented 2 years ago

Also seeing this in https://github.com/conda-forge/pyppmd-feedstock/pull/22

chrisburr commented 2 years ago

This is being discussed on gitter at: https://gitter.im/conda-forge/conda-forge.github.io?at=62b468f2904f20479a190b5b

The cause is a combination of:

conda using hardlinks when installing
crossenv/cross-python applying it's hacky fixes to make a cross-compilation environment

h-vetinari commented 2 years ago

@chrisburr Great, thanks for analyzing and fixing this so quickly!

h-vetinari commented 2 years ago

Confirming as fixed by https://github.com/conda-forge/cross-python-feedstock/pull/44

xylar commented 2 years ago

@chrisburr and others, I'm still seeing this in: https://github.com/conda-forge/keyring-feedstock/pull/88

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: 2653 bytes

Am I doing something weird there or is this issue not completely fixed yet?

xylar commented 2 years ago

To answer my own question, it seems like migration to pypy38 got closed without merging on that feedstock and should probably fix the problem.

traversaro commented 2 years ago

We had a similar error in https://github.com/conda-forge/hpp-fcl-feedstock/pull/65 as well.

xylar commented 2 years ago

@chrisburr, are you able to apply the fix that you had for pypy 3.8 and 3.9 to pypy 3.7 for feedstocks that have not yet been able to migrate?

chrisburr commented 2 years ago

PyPy 3.7 isn't supported by conda-forge anymore so I can't easily.

It's probably possible to hack together something to get conda-forge/cross-python-feedstock to build for PyPy 3.7 again if someone is sufficiently motivated though I'm not going to be able to dedicate time to it. The best solution is probably to remove the PyPy 3.7 migration from feedstocks that haven't been able to accept the PyPy 3.8+3.9 migration.

xylar commented 2 years ago

The best solution is probably to remove the PyPy 3.7 migration from feedstocks that haven't been able to accept the PyPy 3.8+3.9 migration.

Yes, I think that does seem like the right thing to do. @traversaro, is that an option for you all?

traversaro commented 2 years ago

Yes, I suggested something similar in the PR, as I do not think there are a lot of pypy37 + aarch/ppc64 users at all.