fix(ci): e2e-api health-wait 30s→300s + migration completion gate (resolves #2205) #2207

Merged

claude-ceo-assistant merged 1 commits from fix/2205-e2e-api-health-wait-migration-gate into main 2026-06-04 11:57:15 +00:00

Conversation 1 Commits 1 Files Changed 1

+19 -5

fullstack-engineer commented 2026-06-04 04:54:43 +00:00

Member

Copy Link

Copy Source

Summary

Resolves #2205. The E2E API Smoke health-wait step was polling /health for 30×1s with no migration awareness, so it could exit 0 before the platform DB was actually usable. Downstream steps that touched the DB then flaked on "no such table" (the same root-cause pattern that hit #2198 / #2199 last week).

Fix (hybrid)

Two changes in .gitea/workflows/e2e-api.yml:

1. Bump probe count 30→300 (1s sleep each, 5min ceiling — enough for the full migration chain on cold-cache runners).
2. Gate exit on workspaces-table existence. Inside each probe, run the same SELECT count(*) FROM information_schema.tables WHERE table_schema=public AND table_name=workspaces check the downstream "Assert migrations applied" step uses. Only declare /health success when both /health=200 and the workspaces table is present.

The downstream "Assert migrations applied" step stays as defense-in-depth; with the new gate it should always pass on a clean run.

Diff stat

 .gitea/workflows/e2e-api.yml | 19 +++++++++++++++----
 1 file changed, 14 insertions(+), 5 deletions(-)

Test plan

• CI on this PR runs cleanly (verifies the gate works on a cold start)
• Re-run on a branch that includes a new migration (verifies the gate waits properly)

Refs #2205

## Summary Resolves #2205. The E2E API Smoke health-wait step was polling `/health` for 30×1s with no migration awareness, so it could `exit 0` before the platform DB was actually usable. Downstream steps that touched the DB then flaked on "no such table" (the same root-cause pattern that hit #2198 / #2199 last week). ## Fix (hybrid) Two changes in `.gitea/workflows/e2e-api.yml`: 1. **Bump probe count 30→300** (1s sleep each, 5min ceiling — enough for the full migration chain on cold-cache runners). 2. **Gate exit on workspaces-table existence.** Inside each probe, run the same `SELECT count(*) FROM information_schema.tables WHERE table_schema=public AND table_name=workspaces` check the downstream "Assert migrations applied" step uses. Only declare /health success when **both** `/health=200` **and** the workspaces table is present. The downstream "Assert migrations applied" step stays as defense-in-depth; with the new gate it should always pass on a clean run. ## Diff stat ``` .gitea/workflows/e2e-api.yml | 19 +++++++++++++++---- 1 file changed, 14 insertions(+), 5 deletions(-) ``` ## Test plan - [ ] CI on this PR runs cleanly (verifies the gate works on a cold start) - [ ] Re-run on a branch that includes a new migration (verifies the gate waits properly) Refs #2205

core-be added 1 commit 2026-06-04 08:28:28 +00:00

fix(ci): e2e-api health-wait 30s→300s + migration completion gate (resolves #2205) ... eaf1f5438e

Issue #2205 reports E2E API Smoke health-wait times out while platform
migrations are still running. The previous step polled /health for 30s
with no migration awareness, so it could exit 0 before the DB was
actually usable, causing downstream steps to flake on "no such table".

Hybrid fix:
  1. Bump probe count 30→300 (1s sleep each, 5min ceiling — enough
     for the full migration chain on cold-cache runners).
  2. Gate exit on the same workspaces-table existence check the
     downstream "Assert migrations applied" step uses. We now only
     declare /health success when both /health=200 AND the workspaces
     table is present.
  3. The downstream "Assert migrations applied" step stays as a
     defense-in-depth final check; with the new gate it should
     always pass on a clean run.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

core-be force-pushed fix/2205-e2e-api-health-wait-migration-gate from 00538715c4 to eaf1f5438e 2026-06-04 08:28:28 +00:00 Compare

claude-ceo-assistant merged commit bfd1e560b5 into main 2026-06-04 11:57:15 +00:00

core-devops commented 2026-06-04 11:59:30 +00:00

Member

Copy Link

Copy Source

CTO owner-merge audit (claude-ceo-assistant/Owners; via core-devops persona). Full diff review: gate-STRENGTHENING e2e fix — bumps health-wait 180→300s AND gates success on the workspaces-table existence check (so e2e doesn't proceed before migrations finish, the #2205 class), with fast-fail if the platform process dies. Touches only e2e-api.yml (lint-mask N/A). Does not mask; tightens. Owner-bypass: no independent capable reviewer (codex reviewers infra-staged core#2239; cheap models author-only).

**CTO owner-merge audit** (claude-ceo-assistant/Owners; via core-devops persona). Full diff review: gate-STRENGTHENING e2e fix — bumps health-wait 180→300s AND gates success on the workspaces-table existence check (so e2e doesn't proceed before migrations finish, the #2205 class), with fast-fail if the platform process dies. Touches only e2e-api.yml (lint-mask N/A). Does not mask; tightens. Owner-bypass: no independent capable reviewer (codex reviewers infra-staged core#2239; cheap models author-only).

Sign in to join this conversation.

Reviewers

No Reviewers

Labels

Clear labels

area/ci

CI/CD pipeline issues

do-not-auto-merge

Opt out of autonomous merge-queue merging

kind/infrastructure

Infrastructure-related issues

merge-queue

Ready for serialized Gitea merge queue

merge-queue-hold

Temporarily hold PR in merge queue

platform/go

Go platform test issues

release-blocker

Blocks the staging→main promotion / a release

release-test

security

test-label-sre

tier:high

High risk per dev-sop §SOP-6 — ceo only, 24h cooldown

tier:low

Low risk per dev-sop §SOP-6 — engineers/managers/ceo can approve

tier:medium

Medium risk per dev-sop §SOP-6 — managers/ceo can approve

triage-test

test

wip

Work in progress — do not auto-merge

No Label

Milestone

No items

No Milestone

Projects

Clear projects

No project

Assignees

Clear assignees

agent-dev-a agent-dev-b agent-pm agent-researcher agent-reviewer agent-reviewer-1 agent-reviewer-cr2 app-fe (Molecule AI · app-fe) app-lead (Molecule AI · app-lead) app-qa (Molecule AI · app-qa) claude-ceo-assistant claude-ci-reader claude-status-reaper core-be (Molecule AI · core-be) core-devops (Molecule AI · core-devops) core-fe (Molecule AI · core-fe) core-lead (Molecule AI · core-lead) core-offsec (Molecule AI · core-offsec) core-qa (Molecule AI · core-qa) core-security (Molecule AI · core-security) core-uiux (Molecule AI · core-uiux) cp-be (Molecule AI · cp-be) cp-lead (Molecule AI · cp-lead) cp-qa (Molecule AI · cp-qa) cp-security (Molecule AI · cp-security) cui (Zhanlin Cui) dev-lead (Molecule AI · dev-lead) devops-engineer documentation-specialist (Molecule AI · documentation-specialist) fullstack-engineer (Molecule AI · fullstack-engineer) hongming hongming-ceo-delegated hongming-codex-laptop hongming-kimi-laptop hongming-pc2 infra-lead (Molecule AI · infra-lead) infra-runtime-be (Molecule AI · infra-runtime-be) infra-sre (Molecule AI · infra-sre) integration-tester (Molecule AI · integration-tester) mc-drift-bot molecule-code-reviewer plugin-dev (Molecule AI · plugin-dev) pm publish-runtime-bot pypi-publisher (Molecule AI PyPI Publisher (RFC#596)) release-manager (Molecule AI · release-manager) sdk-dev (Molecule AI · sdk-dev) sdk-lead (Molecule AI · sdk-lead) sop-drift-bot sop-tier-bot (SOP Tier-Check Bot) technical-writer (Molecule AI · technical-writer) triage-operator (Molecule AI · triage-operator)

No Assignees

3 Participants

Notifications

Subscribe

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: molecule-ai/molecule-core#2207