It will still run cross-compilation to armhf, but run the binaries on the hardware itself, not qemu.
There shouldn't be any significant difference, other than maybe a slight speedup.
It will still run cross-compilation to armhf, but run the binaries on the hardware itself, not qemu.
There shouldn't be any significant difference, other than maybe a slight speedup.
See https://github.com/cirruslabs/cirrus-ci-docs/pull/905 for pre-merge documentation
Approach ACK
<!--e57a25ab6845829454e8d69fc972939a-->
The following sections might be updated with supplementary metadata relevant to reviewers and maintainers.
<!--174a7506f384e20aa4161008e828411d-->
Reviewers, this pull request conflicts with the following ones:
If you consider this pull request important, please also help to review the conflicting pull requests. Ideally, start with the one that should be merged first.
ACK fa23442ef1581e65f495460f5caae1f6b0582cbf.
Maybe the second commit should be mentioned in the PR description?
Concept ACK
It looks like a full fresh build with functional tests takes 1 hour (24 minutes with cache).
Though, given that the functional tests on arm haven't found issues (https://github.com/bitcoin/bitcoin/pull/20072#issuecomment-703214314), we can skip them for an even faster build. So I've removed the second commit again.
The cached build without functional tests finished in 15 minutes, which is 10 minutes less than with qemu. :rocket:
re-ACK fa35efa84bb614df9629076e45e9e974d9e940f6