molecule-ai/molecule-core
52
0
Fork 2
Code Issues 178 Pull Requests 36 Actions 2 Packages Projects Releases Wiki Activity

[core-lead-agent] DISCOVERY: CI/all-required passes before Platform(Go) completes — Gitea dependency race #1167

New Issue
Open
opened 2026-05-15 10:36:48 +00:00 by core-lead · 0 comments
core-lead commented 2026-05-15 10:36:48 +00:00
Member
Copy Link
Copy Source

Summary

The CI / all-required aggregator job (.gitea/workflows/ci.yml) has needs: [platform-build, ...] but is passing in ~10s while CI / Platform (Go) is still running (takes 15-25m on cold runners). This means all-required does NOT reliably gate on Platform(Go) — PRs can have all-required✅ while Go tests are failing.

Evidence

PRs #1157, #1165, #1109, #1110, #1113 all show CI / all-required ✅ (10s) while CI / Platform (Go) ❌ (Failing after 13-16m).

Root cause hypothesis: Gitea Actions evaluates all-required job readiness based on platform-build job status at queue time. Since platform-build starts quickly (compilation) but the actual test suite runs later, all-required passes before the test suite completes and fails.

Impact

all-required ✅ is insufficient evidence for merge readiness. The Platform (Go) status must be checked independently. Branch protection pointing at all-required does NOT protect against Go test failures.

Suggested fix

Investigate Gitea Actions dependency evaluation timing. Possible fixes:

  1. Add a synthetic status dependency: have platform-build POST a status AFTER tests complete, and have all-required depend on that.
  2. Move all-required to depend explicitly on CI / Platform (Go) context rather than platform-build job.
  3. Add Platform (Go) as an explicit needs: dependency.

Filed by core-lead-agent pulse 10:25 UTC.

## Summary The `CI / all-required` aggregator job (`.gitea/workflows/ci.yml`) has `needs: [platform-build, ...]` but is passing in ~10s while `CI / Platform (Go)` is still running (takes 15-25m on cold runners). This means `all-required` does NOT reliably gate on `Platform(Go)` — PRs can have `all-required✅` while Go tests are failing. ## Evidence PRs #1157, #1165, #1109, #1110, #1113 all show `CI / all-required ✅ (10s)` while `CI / Platform (Go) ❌ (Failing after 13-16m)`. Root cause hypothesis: Gitea Actions evaluates `all-required` job readiness based on `platform-build` job status at queue time. Since `platform-build` starts quickly (compilation) but the actual test suite runs later, `all-required` passes before the test suite completes and fails. ## Impact `all-required ✅` is insufficient evidence for merge readiness. The `Platform (Go)` status must be checked independently. Branch protection pointing at `all-required` does NOT protect against Go test failures. ## Suggested fix Investigate Gitea Actions dependency evaluation timing. Possible fixes: 1. Add a synthetic status dependency: have `platform-build` POST a status AFTER tests complete, and have `all-required` depend on that. 2. Move `all-required` to depend explicitly on `CI / Platform (Go)` context rather than `platform-build` job. 3. Add `Platform (Go)` as an explicit `needs:` dependency. --- Filed by [core-lead-agent](https://github.com/molecule-ai/molecule-core/blob/main/.gitea/workflows/core-lead-agent.yml) pulse 10:25 UTC.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
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
 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) 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#1167
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?