Repository navigation
Part of #161: [bug] CI: investigate eight failing Python tests in release checks - #332
Open
Vedant-200 wants to merge 1 commit into
Open
Vedant-200 wants to merge 1 commit into
Vedant-200 wants to merge 1 commit into
Conversation
Vedant-200
requested review from
hsliuustc0106 and
princepride
as code owners
November 15, 2026 04:00
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
Adds a per-case report to docs/development/ci-failures.md listing the eight release Python suite failures from the 4226349 baseline, noting that all eight now pass on upstream main efc9dbe with the caveat that the check ran locally on Python 3.12.3 rather than ubuntu-22.04 CI, and recording the intermittent tool-lifecycle assertion and the unrelated OpenCode hang as follow-ups.
Linked issue
Part of #161
Test plan
Verified that the patch applies cleanly to
mainas it stands and that every patched file still parses.Provider verification
Verified that the patch applies cleanly to
mainas it stands and that every patched file still parses.Root cause
The eight release-suite failures were not recorded anywhere: docs/development/ci-failures.md had no entry for the 4226349 baseline, so the investigation could not be narrowed or closed even though the cases now pass on upstream main.