Skip to content

[ci] update qemu version pulled in override test#30489

Merged
pamaury merged 1 commit into
lowRISC:earlgrey_1.0.0from
pamaury:update_qemu_ci
Jun 23, 2026
Merged

[ci] update qemu version pulled in override test#30489
pamaury merged 1 commit into
lowRISC:earlgrey_1.0.0from
pamaury:update_qemu_ci

Conversation

@pamaury

@pamaury pamaury commented Jun 22, 2026

Copy link
Copy Markdown
Contributor

This version is very old and does not match the one downloaded by bazel. This old version also does not compile anymore due to a mirror being discontinued.

A different fix was done on master branch, see explanation there #30445

This version is very old and does not match the one downloaded by
bazel. This old version also does not compile anymore due to a
mirror being discontinued.

Signed-off-by: Amaury Pouly <amaury.pouly@opentitan.org>

@AlexJones0 AlexJones0 left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the fix!

If it's possible, it'd be nice in the future if this could use the version pinned in third_party/qemu/extensions.bzl to avoid these becoming out of sync.

@pamaury

pamaury commented Jun 22, 2026

Copy link
Copy Markdown
Contributor Author

Thanks for the fix!

If it's possible, it'd be nice in the future if this could use the version pinned in third_party/qemu/extensions.bzl to avoid these becoming out of sync.

Unfortunately it doesn't seem very easily to sync a yml workflow with a bazel file. I can imagine rather involved ways of doing this but in truth this CI test is really just a sanity check, it doesn't fundamentally matter which version it uses. The issues only arised because a mirror disappeared.

@pamaury pamaury merged commit 798d1eb into lowRISC:earlgrey_1.0.0 Jun 23, 2026
35 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants