Skip to content

test(cli): fix 1 flaky test in live branch create - #7326

Open
avallete wants to merge 1 commit into
developfrom
avallete/flaky-fixes-2026-10-26
Open

avallete wants to merge 1 commit into
developfrom
avallete/flaky-fixes-2026-10-26

Conversation

@avallete

Copy link
Copy Markdown
Member

TL;DR

The live branch helper now re-creates a branch once when the platform drops TLS while setting the branch password, the same way it handles a 57P01 database restart.

  • apps/cli/src/commands/branches/get/get.live.test.ts › gets a preview branch by name: branches create failed with 400: Failed to update password: Client network socket disconnected before secure TLS connection was established. This is a transient platform rejection during create, like the 57P01 restart from test(cli): fix 1 flaky test in live branch create #7256, but the helper only re-issued the create for 57P01. The helper's transient-rejection matcher now also covers this documented TLS drop, so it runs the same single clear-and-recreate. A second rejection still fails. create.live uses the same helper and gets the fix too.

ref

spotted in:


Generated by Claude Code

The platform rejects `branches create` with a 400 when its TLS connection
drops while setting the branch database password. Treat that rejection like
the 57P01 restart in the helper's single clear-and-recreate.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_014y76TaNM2eKGdpmiMQXWqu
@avallete
avallete requested a review from a team as a code owner October 26, 2026 07:42

Copy link
Copy Markdown
Member Author

/ai-review


Generated by Claude Code

@github-actions github-actions Bot left a comment •

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Superseded by a newer AI review

🤖 AI Review

Both independent reviews reported no findings. Reading the changed helper and surrounding tests confirms that the TLS failure uses the existing cleanup-and-retry path, retries only once, and preserves subsequent failures. No actionable issues or fundamental conflicts with the supplied next-branch context were found. Tests were not run because dependencies are not installed.

Findings

No issues found.

Stats

Claude findings: 0 · Codex findings: 0 · Confirmed: 0 · Refuted: 0 · Uncertain: 0


Models: claude-opus-5-5 + gpt-6.1-sol · Trigger: auto · Workflow run

This review runs once per PR. A maintainer can request another with a /ai-review comment.

@github-actions github-actions Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🤖 AI Review

Both independent reviews reported no findings. Reading the changed files and surrounding code confirmed that the TLS failure matcher uses the existing single-retry path, preserves cleanup, and propagates a second failure. The regression test covers the new error message. No actionable issues or fundamental next-branch conflicts found. Tests were not run because dependencies are absent.

Findings

No issues found.

Stats

Claude findings: 0 · Codex findings: 0 · Confirmed: 0 · Refuted: 0 · Uncertain: 0


Models: claude-opus-5-5 + gpt-6.1-sol · Trigger: manual · Workflow run

This review runs once per PR. A maintainer can request another with a /ai-review comment.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants