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

[REGRESSION] .gitea/scripts/tests/test_gitea_merge_queue.py — 2 failing tests on staging (mc#1032) #1031

New Issue
Closed
opened 2026-05-14 15:04:08 +00:00 by core-qa · 0 comments
core-qa commented 2026-05-14 15:04:08 +00:00
Member
Copy Link
Copy Source

Regression Description

.gitea/scripts/tests/test_gitea_merge_queue.py has 2 failing tests on origin/staging at SHA 4e8b40d1:

FAILED test_gitea_merge_queue.py::test_merge_decision_requires_main_green_pr_green_and_current_base
  AssertionError: assert 'pause' == 'merge'

FAILED test_gitea_merge_queue.py::test_merge_decision_updates_stale_pr_before_merge
  AssertionError: assert 'pause' == 'update'

Root Cause

Commit e16abf15 ("fix(queue): check push-required contexts explicitly, not combined state") changed evaluate_merge_readiness() to require the "CI / all-required (push)" context in main_status.statuses[] before approving a merge.

The tests still pass main_status={"state": "success", "statuses": []} (empty), so required_contexts_green({}, ["CI / all-required (push)"]) returns (False, ["CI / all-required (push)=missing"]) and the action becomes "pause" instead of the expected "merge" or "update".

Fix

Commit 0b47f951 ("fix(ci): repair delegation list and merge queue tests") on origin/main adds the missing push status to the test mocks:

main_status = {
    "state": "success",
    "statuses": [{"context": "CI / all-required (push)", "status": "success"}],
}

This fix is in origin/main but NOT in origin/staging. The staging branch is missing it.

Action Required

  1. Cherry-pick or apply commit 0b47f951 to the staging branch
  2. Open a PR targeting staging to merge the test fix
  3. Verify tests pass after fix

Labels

  • regression
  • ci
  • test
  • priority:medium
## Regression Description `.gitea/scripts/tests/test_gitea_merge_queue.py` has **2 failing tests on origin/staging** at SHA `4e8b40d1`: ``` FAILED test_gitea_merge_queue.py::test_merge_decision_requires_main_green_pr_green_and_current_base AssertionError: assert 'pause' == 'merge' FAILED test_gitea_merge_queue.py::test_merge_decision_updates_stale_pr_before_merge AssertionError: assert 'pause' == 'update' ``` ## Root Cause Commit `e16abf15` ("fix(queue): check push-required contexts explicitly, not combined state") changed `evaluate_merge_readiness()` to require the "CI / all-required (push)" context in `main_status.statuses[]` before approving a merge. The tests still pass `main_status={"state": "success", "statuses": []}` (empty), so `required_contexts_green({}, ["CI / all-required (push)"])` returns `(False, ["CI / all-required (push)=missing"])` and the action becomes `"pause"` instead of the expected `"merge"` or `"update"`. ## Fix Commit `0b47f951` ("fix(ci): repair delegation list and merge queue tests") on origin/main adds the missing push status to the test mocks: ```python main_status = { "state": "success", "statuses": [{"context": "CI / all-required (push)", "status": "success"}], } ``` This fix is **in origin/main but NOT in origin/staging**. The staging branch is missing it. ## Action Required 1. Cherry-pick or apply commit `0b47f951` to the staging branch 2. Open a PR targeting staging to merge the test fix 3. Verify tests pass after fix ## Labels - regression - ci - test - priority:medium
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#1031
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?