molecule-ai/molecule-core
52
0
Fork 2
Code Issues 184 Pull Requests 16 Actions 3 Packages Projects Releases Wiki Activity

[main-red] E2E API Smoke health wait times out while platform migrations are still running #2205

New Issue
Closed
opened 2026-06-04 04:30:07 +00:00 by molecule-code-reviewer · 0 comments
molecule-code-reviewer commented 2026-06-04 04:30:07 +00:00
Member
Copy Link
Copy Source

MECHANISM: molecule-core main 0ad52852fd38 fails E2E API Smoke Test / E2E API Smoke Test because .gitea/workflows/e2e-api.yml:330-342 gives platform-server only 30 one-second health probes after background start. On this run, platform startup is still applying the full migration chain during that window; the log reaches migrations through 20260523000000_schedule_consecutive_sdk_errors.up.sql and only then prints Platform starting on :45089. The health loop expires before /health becomes reachable, so downstream E2E assertions never run.

EVIDENCE: job 274520 (run 206111, head 0ad52852fd387a107eefc1d25348a3fb707cd8f2) failed at 2026-06-04T04:27:31Z. Log excerpt: Platform did not become healthy in 30s. The dumped workspace-server/platform.log shows migrations still applying at 04:26:15-04:26:26, then Platform starting on :45089 immediately after the health failure block. Workflow line .gitea/workflows/e2e-api.yml:333 hard-codes seq 1 30.

RECOMMENDED FIX SHAPE: responsible file is molecule-core/.gitea/workflows/e2e-api.yml. Increase or make adaptive the /health wait for the real migration replay path, ideally polling until platform startup or migration completion within the job timeout and surfacing the last migration/log tail on failure. Do not weaken the E2E API gate; make the readiness window match the current migration-chain startup cost.

MECHANISM: molecule-core main `0ad52852fd38` fails `E2E API Smoke Test / E2E API Smoke Test` because `.gitea/workflows/e2e-api.yml:330-342` gives platform-server only 30 one-second health probes after background start. On this run, platform startup is still applying the full migration chain during that window; the log reaches migrations through `20260523000000_schedule_consecutive_sdk_errors.up.sql` and only then prints `Platform starting on :45089`. The health loop expires before `/health` becomes reachable, so downstream E2E assertions never run. EVIDENCE: job `274520` (`run 206111`, head `0ad52852fd387a107eefc1d25348a3fb707cd8f2`) failed at `2026-06-04T04:27:31Z`. Log excerpt: `Platform did not become healthy in 30s`. The dumped `workspace-server/platform.log` shows migrations still applying at `04:26:15`-`04:26:26`, then `Platform starting on :45089` immediately after the health failure block. Workflow line `.gitea/workflows/e2e-api.yml:333` hard-codes `seq 1 30`. RECOMMENDED FIX SHAPE: responsible file is `molecule-core/.gitea/workflows/e2e-api.yml`. Increase or make adaptive the `/health` wait for the real migration replay path, ideally polling until platform startup or migration completion within the job timeout and surfacing the last migration/log tail on failure. Do not weaken the E2E API gate; make the readiness window match the current migration-chain startup cost.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
approved
area/ci
CI/CD pipeline issues
 do-not-auto-merge
Opt out of autonomous merge-queue merging
 do-not-merge
hold from auto-merge (design review in progress)
 kind/infrastructure
Infrastructure-related issues
 merge-queue
Ready for serialized Gitea merge queue
 merge-queue-hold
Temporarily hold PR in merge queue
 needs-engineer
platform/go
Go platform test issues
 ready-to-build
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) godwin hongming hongming-ceo-delegated hongming-codex-laptop hongming-kimi-laptop hongming-pc2 hongming-personal 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
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: molecule-ai/molecule-core#2205
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?