Repository navigation
Exercise Mere shell and offline builds in the QEMU guest - #639
Merged
Merged
Conversation
9 tasks done
1 of 4 tasks
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
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.
The disk guest previously verified dinit boot without exercising Mere itself. Add
test/qemu/mere-smoke, reusing the existing preparation and boot flow, to run the supplied static Mere binary inside the guest, enter a profile, build a tiny recipe, and validate the resulting archive payload.Guest builds run offline against copied upstream signed metadata and downloaded packages. An intentionally failing recipe must make Mere return 1, report the recipe's exit code 7, and produce no package. Results retain serial output, input identities, ELF headers, repository hashes, and fixture sources. The guest root now includes
/home, required by Mere shell's bind mounts.Host setup/replay still requires network access and repository retention. Production service lifecycle and bootloader validation remain separate under #634.
Closes #635.