Bump QEMU and release 4.1.1 again #439
Merged
Conversation
This file contains 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
stanmart
requested review from
MarcAntoineSchmidtQC,
jtilly and
lbittarello
as code owners
|
fyi @mlondschien |
jtilly
approved these changes
Jan 30, 2025
1 task
|
thank you! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Yesterday's 4.1.1 release did not go well, as there were a bunch of segfaults while building jemalloc for linux-aarch64. As it turns, out, we have been using a rather old QEMU version, because the
setup-qemu-actionpulls the image with thelatesttag. It seems sensible enough, but as it turns out, this tag has not been updated for the relevant container in more than two years.Switching to an up-to-date QEMU seems to solve the problem, Therefore I propose upgrading to this recent QEMU version and attempting a new release today.
Checklist
CHANGELOG.rstentry