ci: run RPC end-to-end check on local cluster - #74
Merged
Conversation
📊 Criterion benchmarks: main vs PR🔍 Main 📊 25 benchmark(s) compared · ℹ️ Time is lower-is-better. Both revisions ran on the same GitHub-hosted VM; ±20% is an advisory marker, not a merge gate.
|
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.
Closes #64.
Summary
rpc_e2ein the post-merge Cluster E2E workflow and emit RPC-proxy logs on failureValidation
bash -n tests/cluster-e2e/run_local_cluster.shcargo fmt --checkcargo test --workspacecargo test --doccargo clippy --workspace --all-targets -- -D warningsThe live Docker check was not run locally because a user-owned
yt.frontendcontainer is already using the local stack name.