Gerrrr commented on PR #149: URL: https://github.com/apache/otava/pull/149#issuecomment-4293005202
> Did you run this somewhere? I assume yes, but if so, where should I expect to see docker images coming through on the other side > Why? These are connected stories :) First, I added buildx to tox and CI to build the image for both architectures. The CI succeeded, but took 4 times longer (36 minutes instead of 9). While waiting for that CI job to finish, I decided to run it locally to find the potential issues sooner. On my personal laptop, `uv run tox -e docker-build` failed with out of memory error while building numpy. It turned out that building numpy via QEMU takes forever AND consumes a ton of memory as it builds a bunch of C/C++ libraries. Why did the docker-build build numpy instead of just using the wheels? Numpy provides wheels for Python 3.14 only starting with version `2.3.2`... but that version only supports Python >=3.11. The combination of these issues lead me to upgrading numpy for Python 3.14 which in turn enabled fast cross-arch builds. As a result of these changes, GH CI runs in 4.5 minutes instead of 9/36 (baseline/multiarch) and does not crash with cryptic errors on Macbook Air 2022. > where should I expect to see docker images coming through on the other side. We do not have yet a release CI job automating publishing to Dockerhub and PyPI. For the release process, you'll need to 1) check out the accepted version's tag and 2) build locally, then push to Dockerhub. I updated the release instructions in this PR. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
