ci: temporarily disable flaky progress conformance scenario - #106
Merged
Conversation
Signed-off-by: lucarlig <luca.carlig@ibm.com>
lucarlig
marked this pull request as ready for review
August 20, 2026 09:25
Signed-off-by: Luca <luca.carlig@ibm.com>
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
2 participants
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
tools-call-with-progressfrom the expected-failure baseline0.2.0-alpha.11has no scenario-exclusion optionWhy
Progress notifications and the final response are processed by separate tasks. Depending on scheduling, cleanup can happen before progress forwarding completes, so the scenario can either pass or fail. An expected-failure entry is unsuitable because a passing run becomes an XPASS and fails CI.
This is temporary until progress forwarding and final-response cleanup are ordered deterministically.
Verification
tests/conformance/report-baseline-diff-test.shtests/conformance/disable-flaky-progress.patchagainst pinned conformance SHAc321dd32035556e6769d3724a8ee97d87c3faaacgit diff --checkcargo nextest run --locked --workspace