Repository navigation
test: prove current Node live-mutex dev with nine clients - #13
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.
Funded exact-head promotion evidence for current
ORESoftware/live-mutexdevat9cdf46dbd0768697d784be01ebbf0aade38bfa85.This reproduces the repository's own nine-client E2E contract on a funded runner and asserts the source workflow blob before execution. It builds the exact Node broker and exercises all nine maintained client languages against it: Rust, Python, Shell, PowerShell, Go, Dart, Java, C++, and Gleam.
This is separate from the CircleCI modernization reproduction for #176; its purpose is to keep the original cross-language broker requirement proven on current Node
deveven when the source org's Actions capacity is unreliable.