Add qemu_x86_64 to Zephyr CI - #1788
Open
Bhoumik Patidar (BhoumikPatidar) wants to merge 1 commit into
Open
Conversation
Bhoumik Patidar (BhoumikPatidar)
requested review from
quic-areg and
Shankar Easwaran (quic-seaswara)
August 28, 2026 19:05
Bhoumik Patidar (BhoumikPatidar)
force-pushed
the
add-x86_64-zephyr-workflow
branch
from
August 28, 2026 19:06
860d86b to
6d56673
Compare
Shankar Easwaran (quic-seaswara)
approved these changes
Aug 28, 2026
Adds toolchain input to zephyr-run.yml, defaulting to cpullvm for existing backends and a qemu_x86_64 backend using GCC from the Zephyr SDK. Adds a step applying KEEP rules to Zephyr's linker scripts for the C++ exception tables, to be dropped once they land upstream Also adds --retry-failed for flaky tests and --personal-access-token to avoid GitHub API rate limits. Signed-off-by: Bhoumik Patidar <bpatidar@qti.qualcomm.com>
Bhoumik Patidar (BhoumikPatidar)
force-pushed
the
add-x86_64-zephyr-workflow
branch
from
August 28, 2026 19:10
6d56673 to
940c8e2
Compare
Bhoumik Patidar (BhoumikPatidar)
marked this pull request as ready for review
August 28, 2026 19:23
quic-areg
reviewed
Aug 28, 2026
quic-areg
left a comment
quic-areg
left a comment
Contributor
There was a problem hiding this comment.
How does this work without upstream eld build support with GCC?
| -x=CONFIG_LLVM_USE_ELD=y \ | ||
| -x=CONFIG_COMPILER_RT_RTLIB=y \ | ||
| --retry-failed 2 \ | ||
| --retry-interval 10 \ |
Contributor
There was a problem hiding this comment.
Should we quarantine these tests instead? My concern is that an intermittent linker failure could still produce a green result and we know about it. Runtime might also be a concern currently since the builds are close to the 6h gh limit.
Contributor
There was a problem hiding this comment.
How long does this take ?
I think the retry is needed even with bfd.
Contributor
are you referring to using clang instead of gcc ? |
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
3 participants
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.
Adds
x86_64as a sixth board. It builds with GCC from the Zephyr SDK.Adds toolchain input to
zephyr-run.yml, defaulting tocpullvmfor existing backends and aqemu_x86_64backend using GCC from the Zephyr SDK. Adds a step applying KEEP rules to Zephyr's linker scripts for the C++ exception tables, to be dropped once they land upstreamAlso adds
--retry-failedfor flaky tests and--personal-access-tokento avoid GitHub API rate limits.