Open h-vetinari opened 1 month ago
The old logs are lost (so harder to analyze what changed), but it seems that this now works...? 🤔
Intriguing. I would have assumed that https://github.com/conda/conda-build/pull/5350 was responsible for the fix, but that's not released yet :/
aaaaand, it broke again (only difference was inclusion of sparse
or not as a test dependence). I'll recheck again after #5350 is released.
Can confirm that with conda-build installed from main
, this now passes 🥳
Checklist
What happened?
We recently split up the
pyarrow
package into more bits and pieces (e.g. distinguish minimal variant for small footprint from full-featured "give me everything"), and now we have a sandwich where the first and last package in a telescopic chain of dependencies are per python, whereas there are two empty metapackages in the middle that could easily be noarch:I've tried doing that in https://github.com/conda-forge/pyarrow-feedstock/pull/119, and it works fine in native builds, but fails with non-sensical errors on aarch/ppc:
When I say non-sensical, I mean that that the
TEST END:
at the top just confirmed the local existence of an artefact that should match the requested pattern. Looking closer, what's happening isi.e. the build switches architecture when getting to the noarch output.
Note that all jobs in that PR want to build:
which is the goal - we need to build it in each job in order to successfully build the per-python
pyarrow-tests
on top, but only one build would be uploaded in the end across all jobs, due to the (intentional!) hash collision.Conda Info
No response
Conda Config
No response
Conda list
No response
Additional Context
No response