fix: split CPU docker build into native amd64/arm64 jobs to prevent 6h timeout#1418
Merged
sbryngelson merged 7 commits intoMay 11, 2026
Merged
Conversation
…h timeout The CPU container job was using QEMU to cross-compile linux/arm64 on a single x86 runner, consistently hitting the 6-hour GitHub Actions limit. All recent releases (v5.1.3 through v5.3.1) failed to publish latest-cpu. Fix: split into two native jobs (ubuntu-22.04 and ubuntu-22.04-arm), mirroring the existing GPU build pattern. Remove QEMU. Merge into a multi-arch manifest in the manifests job using buildx imagetools. Also: add weekly schedule trigger (Sunday midnight UTC) so the devcontainer image stays fresh between releases, and bump build-push-action to v6.
Contributor
ⓘ You've reached your Qodo monthly free-tier limit. Reviews pause until next month — upgrade your plan to continue now, or link your paid account if you already have one. |
This was referenced May 11, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
latest-cpudevcontainer image has never successfully published since v5.1.3 because the CPU build job consistently hits GitHub Actions' 6-hour limitlinux/arm64on a single x86 runner alongsidelinux/amd64, which takes >6h to compile MFCubuntu-22.04for amd64,ubuntu-22.04-armfor arm64), mirroring the existing GPU build pattern — each finishes in ~1hChanges to
docker.ymlcpuentry forubuntu-22.04-arm; remove QEMU emulation from the CPU job entirelyplatforms: linux/amd64,linux/arm64and the custommfcbuilder; tags now include the runner name (e.g.$TAG-cpu-ubuntu-22.04-arm) matching GPU conventionbuildx imagetools createuniformly for both CPU and GPU manifest listscron: '0 0 * * 0'weekly rebuild frommaster, tagged asnightlybuild-push-action@v5→v6; makeworkflow_dispatchtag optionalTest plan
fix/docker-cpu-timeoutbranch workflow runs complete without the CPU job timing outlatest-cpumanifest resolves bothlinux/amd64andlinux/arm64after a successful run