debug: investigate sdk bindings drift on CI (temporary) - #120
Closed
collinsezedike wants to merge 1 commit into
Closed
debug: investigate sdk bindings drift on CI (temporary)#120collinsezedike wants to merge 1 commit into
collinsezedike wants to merge 1 commit into
Conversation
Collaborator
Author
|
Diagnostic complete: confirmed the sdk job's earlier failures on #117 were non-deterministic build flakes, not a real bindings drift (sha256sum showed byte-identical output on a from-scratch Linux build). Closing this, not for merge. |
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.
Not for merge. Diagnostic PR carrying PR #117's contracts/tholos + packages/tholos-sdk changes plus a temporary CI tweak that prints the full diff and wasm/index.ts hashes, to see the actual mismatch content the sdk job's drift check is reporting on Linux (four separate local Windows rebuilds all matched exactly, so this is to observe the real difference on the CI runner itself). Will close once we understand root cause.