test(e2e 614): ask mcpp where its store is, do not guess - #578
Merged
Conversation
The store was derived from `${MCPP_HOME:-$HOME/.mcpp}` while the BINARY under
test resolves its home from its own location: a released mcpp carries a
`registry/` beside itself. Pointed at a released tarball the test failed about
features while really measuring a path mismatch.
The same guess cost a CI job in llama.cpp-m on the same day, which is why this
is worth a commit rather than a note: it is one fact with two readers, and both
were guessing.
`mcpp index status` names a path under the home the binary actually uses, and
the environment default remains the fallback for a build that has no index yet.
Measured: passes against the locally built binary and against the released
2026.9.6.2 tarball, and still exits 1 against the binary predating the engine
fix it exists for.
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
2 participants
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.
What
e2e 614 derived the payload store from
${MCPP_HOME:-$HOME/.mcpp}while thebinary under test resolves its home from its own location — a released mcpp
carries a
registry/beside itself.Pointed at the released 2026.9.6.2 tarball the test therefore failed about
features while really measuring a path mismatch.
Why it is worth a commit rather than a note
The same guess cost a CI job in
llama.cpp-mon the same day: its Vulkan jobsearched
${HOME}/.mcppfor the lavapipe ICD while the payloads sat under$RUNNER_TEMP. One fact, two readers, both guessing.The fix
mcpp index statusnames a path under the home the binary actually uses. Theenvironment default remains the fallback for a build that has no index yet.
Measured
The last row is the one that matters: the test still says no to what it was
written to catch.