Fix QEMU crash in multi-arch frontend build - #3
Merged
Merged
Conversation
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.
Correctif
Le build multi-architecture exécutait
npm cidans le stage frontend arm64 sous QEMU. Node a reçu unSIGILL(Illegal instruction), puis Buildx est resté bloqué jusqu’à l’annulation du workflow.Le bundle Vite est composé de fichiers statiques indépendants de l’architecture. Le stage frontend utilise désormais
--platform=$BUILDPLATFORM: il est construit une seule fois nativement sur le runner, puis copié dans les runtimes amd64 et arm64.La version documentée passe à 1.16.2 afin de ne pas déplacer le tag v1.16.1 déjà poussé.
Validation