Transient qemu error also causes build-containers job to hang
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 8
- Forks
- 7
- Avg merge
- 2d 5h
- Merged PRs (30d)
- 62
Description
I noticed a build-containers CI job on a PR was hung up for 2+ hours and not progressing. The last message in the "Build and Push Docker Image" step was:
#18 [linux/arm64 builder 5/5] RUN npm install --save @notionhq/notion-mcp-server@1.9.0
#18 24.34 qemu: uncaught target signal 4 (Illegal instruction) - core dumped
A re-run succeeded, so this was a transient error. But I would have expected it to fail out the job immediately, not cause it to hang.
Job: https://github.com/stacklok/dockyard/actions/runs/19502404593/job/55819914543?pr=149
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the build-containers workflow and its "Build and Push Docker Image" step, then review the linked Actions job logs around the qemu illegal-instruction message. Determine why this transient failure leaves the job running; done means the job exits promptly as failed instead of hanging.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, github-actions, node.js
- Domain
- build-system, ci-cd, devops
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100