docker.yml: assert the server survives writes through every POV flavour (#578) - #585
Merged
Merged
Conversation
…ur (#578) The v0.1.0 arm64 image passed the MCP smoke, the in-container orlyc compile and the REPL check while segfaulting just after the first write through a POV. Each of those smokes stops looking as soon as its write answers, and #578's crash landed a moment later. After the MCP smoke, write through safe/fast x shared/private, five fresh POVs each, wait five seconds, and require the container to still be running with exit 0 and no restarts. Checked locally against the published images: v0.1.0 arm64 dies under the step (exit 139); v0.1.1 arm64 answers all 20 writes and stays up.
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.
The
v0.1.0arm64 image passed every gate indocker.yml(the MCP smoke, the in-containerorlyccompile, the REPL check) while segfaulting just after the first write through a POV (#578). Each of those smokes stops looking as soon as its write answers, and the crash landed a moment later.This adds one step after the MCP smoke. It writes through all four POV flavours (
safe/fast×shared/private), five fresh POVs each, waits 5s, and requiresdocker inspectto reportrunning exit=0 restarts=0. It runs on both arches, on PRs that touch the image and on every publish.Verified locally against the published images (native arm64)
v0.1.0exited exit=139, so the step failsv0.1.120 writes answered, containerrunning exit=0 restarts=0, so the step passesThe step runs after the MCP smoke, which has already installed
sample. The local test installed it first too, to make sure the secondinstalldoesn't error.This PR touches
docker.yml, so its own CI builds both images and runs the new step on each.