Repository navigation
test(ci): align release expectations with provider behavior - #10236
Merged
Merged
Conversation
4 tasks done
muhamadgalihsaputra
pushed a commit
to niyatna/NiyatnaRoute
that referenced
this pull request
Sep 27, 2026
…inference#10236) * test(xai): align executor expectations with Responses * test(ci): align release expectations with provider behavior --------- Co-authored-by: backryun <bakryun0718@proton.me>
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.
Summary
release/v3.8.50unit-shard base-red reproduced while validating PR fix: repair Audio Bridge runtime multipart self-loop #10229Root causes
xai-oauth/grok-4.5from Chat Completions to the Responses contract, but two older assertions still expected/chat/completionsandmessages.cache_control.ttlvalues to1h, but five older assertions still expected only{ type: "ephemeral" }.xhightohighfor models that do not declare extra-high support, but one AIO assertion still expectedxhigh.The new feature-specific regression tests were green in every case; only the stale expectations failed.
TDD proof — Local VPS 192.168.0.15
First red/green cycle, xAI:
Second red/green cycle, Claude cache TTL and provider reasoning sanitization:
Combined VPS command:
The same three changed files passed ESLint on the VPS with the repository's official suppression baseline.
Scope
Changed files:
tests/unit/executor-xai.test.tstests/unit/chatcore-translation-paths.test.tstests/unit/cc-compatible-provider.test.tsNo changelog fragment: this PR only reconciles stale tests with already documented and merged production behavior.