ci: move SDK tests into CLI job - #1773
Merged
Merged
Conversation
limityan
marked this pull request as ready for review
July 26, 2026 08:07
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.
Summary
Why
SDK-specific tests were duplicated in the long-running Rust matrix even though the CLI job already owns the SDK Host package tests. Keeping them in the CLI job shortens the matrix without dropping the test suites.
Impact
SDK tests now run in the Ubuntu CLI job instead of being repeated across the Rust OS matrix. The matrix still compiles the full workspace on Linux, macOS, and Windows, and the Windows ConPTY CLI smoke remains platform-gated there.
Validation