pythonfastavro/fastavro #678Not a task: already works

aarch linux wheels (again?)

envgap__fastavro__fastavro-678

Original GitHub issue ↗Dated source checkout ↗Opened 2023-03-06

01 / FAILURE SIGNATURE

As reported upstream

No identifying execution failure has been captured.

Not a benchmark task.

The project already builds and runs before the fix, so there is nothing to repair.

02 / ENVIRONMENT RECIPE

Base commit: 0af9c80ade695f0b945d189d7b973ab55aba35da
Manifest: pyproject.toml
Reproduce: Awaiting issue-specific recipe
Run under trace: Awaiting a meaningful runtime command

03 / ORIGINAL ISSUE TEXT

fastavro/fastavro #678 · read the original issue

I recently tried to pip install on an Alpine distribution and it fell back to doing a source install which was painful (cross platform build).  I think that [the wildcard in "build_linux.yml"](https://github.com/fastavro/fastavro/blob/0af9c80ade695f0b945d189d7b973ab55aba35da/.github/workflows/build_linux.yml#L64) is at fault.  When I manually build the wheel on an Alpine arm64 container, the resulting wheel is named "fastavro-x.y.z-cp31-cp311-linux_aarch64.whl".



Should the wildcard be "dist/*-linux*.whl" instead of "dist/*-manylinux*.whl"?  I think that it should be but I'm not sure if there is a difference between building with cibuildwheel versus `python -m build --wheel` on the target platform.

Continue on GitHub ↗

04 / LABELS

Labels from the report text only; not yet run

No supported category has been assigned.

Label rules and the text that matched

[]