Skip to content

stale-pr: resolve code#2888 — mcpx CI PR held: its own mcpx-test workflow fails (unit + all e2e shards + ci-ok) #3813

Closed

Description

@dezren39

Resolution task for PR #2888 (ci(mcpx): first measured iteration — static e2e shards + unit + lint + ci-ok, #1998).

During the 2026-11-01 merge pass this PR was held (not merged): it is mergeable, but the mcpx-test workflow it introduces fails on its own branch — observed via gh statusCheckRollup:

  • basic: mcpx-test unit — FAILURE
  • basic: mcpx-test e2e (shard 0..5) — FAILURE (all six shards)
  • mcpx-test ci-ok — FAILURE
  • basic: mcpx-test init (static e2e matrix) — SUCCESS
  • basic: mcpx-test lint — SUCCESS

Decision needed: fix the mcpx unit/e2e failures on the branch so the new CI is green on arrival, or — if the failures are the pre-existing baseline #1998 intends to record — adjust the workflow so ci-ok reflects the intended gating and say so on the PR. Then merge.

PR: #2888

Activity

  1. developing-today commented on Nov 1, 2026

    @developing-today
    Contributor
  2. dezren39 commented on Nov 3, 2026

    @dezren39
    MemberAuthor

    🤖 Agent note · handed off

  3. dezren39 commented on Nov 3, 2026

    @dezren39
    MemberAuthor

    Handed off: task 7379 (triage, issue #3813) was claimed by lane code-l and assigned to the opencode execution lane. The laptop claimant launches the bound opencode session, which drives task 7379 to its terminal state. Fresh check at handoff: issue #3813 is OPEN; PR #2888 is MERGED — the claimant should verify whether that closes the tracker for issue #3813.

  4. dezren39 commented on Nov 3, 2026

    @dezren39
    MemberAuthor

    agent-note:v1
    state: picked-up → resolved (closing — the tracked PR landed)
    queue: repo-health-code-pilot
    task: 7379 (triage, worker repo-worker-code, lane 262eb403-3347-4a7c-ba6b-e7bc263ca853)
    by: openchamber-scheduled-lane
    at: 2026-11-03T13:58Z

    Resolution: PR #2888 is merged — this tracker is done

    Fresh state, not the packet's: gh pr view 2888 reports MERGED 2026-11-02T14:39:57Z from queue/3294-1998-mcpx-ci-shards, landing exactly this tracker's subject — .github/workflows/mcpx-test.yml plus the .github/ci-policy.md change it was held behind (files: .github/ci-policy.md, .github/workflows/mcpx-test.yml).

    The tracker's own close condition is "close this tracker when the PR lands or closes", so it is satisfied: the hold/fix decision it was waiting on was taken and the workflow shipped.

    What this does not claim

    The red state this tracker described has not become green — it moved. mcpx-test runs on main are failing right now (latest on main: 2026-11-02T21:40:05Z b0495938, and 2026-11-02T18:22:51Z / 16:25:31Z before it), so "the new CI is green" is still open as a main-health fact, not as a PR-resolution task. That belongs with the existing main-red trackers rather than here: #2534 (main-broken: … mcpx @9f3c829 — basic: test), #2716 (internal/settings / internal/conformance red on clean main), #2846 (internal/settings red on clean main). No new issue is filed — filing a fourth main-red tracker for the same surface is the duplication this queue is trying to avoid; if those three do not cover the current mcpx-test failures, the right fix is to fold them into #2534, not to add another.

    Closing as completed (not planned is wrong here — the work was done; the close reason is completion, and GitHub only offers completed/not-planned, so: completed).

  5. removed
    queue/queuedHas a queued task in the Supabase agent queue
    queue/claimedQueue worker lifecycle state
    work/assignedQueue worker lifecycle state
    on Nov 3, 2026
  6. dezren39 commented on Nov 3, 2026

    @dezren39
    MemberAuthor

    agent-note:v1
    state: done
    queue: repo-health-code-pilot
    task: 7379 (completed, outcome already_done)
    by: openchamber-scheduled-lane
    at: 2026-11-03T13:59Z

    Tracker closed completed — the PR it tracked (#2888) merged 2026-11-02. Labels cleared: work/assigned, queue/claimed, queue/queued, status/in-progress. No branch, no PR opened here, no follow-up task (main-red mcpx-test stays with #2534/#2716/#2846).

  7. added
    queue/queuedHas a queued task in the Supabase agent queue
    source/creatorFiled by the new-issue-creator job
    task/triageQueue packet kind: verify, reproduce, and route this item
    on Nov 3, 2026
  8. dezren39 commented on Nov 3, 2026

    @dezren39
    MemberAuthor

    agent-note:v1
    state: reviewed (coverage loop-back)
    Coverage pass 2026-11-03, loop-back review: this issue was re-reviewed (drift / overlap / already-handled / stale / blockers / ordering) so every open issue in the four repos is reviewed and in the system. Verdict: still live; in the system as task 8294 (triage, claimed, priority 30) in repo-health-code-pilot. Labels audited and synced. If it is already handled at current main, its triage closes it with evidence; if oversized, the triage files the split; blockers belong on this issue.
    Found via: coverage loop-back 2026-11-03

  9. dezren39 commented on Nov 3, 2026

    @dezren39
    MemberAuthor

    🤖 Agent note · handed off

  10. removed
    queue/queuedHas a queued task in the Supabase agent queue
    on Nov 3, 2026
  11. dezren39 commented on Nov 3, 2026

    @dezren39
    MemberAuthor

    agent-note:v1
    state: done
    queue: repo-health-code-pilot
    task: 8294 (completed, outcome already_done)
    by: openchamber-scheduled-lane (repo-worker-code, lane bf419306)
    at: 2026-11-03T19:41Z

    Triage at current main: issue #3813 is CLOSED (completed, 2026-11-03T13:53Z) and PR #2888 is MERGED (2026-11-02, merge commit 34c791f). Nothing left to fix here; no branch, no PR, no follow-up task. Removed the stale queue/queued label. Main-red mcpx-test stays with #2534/#2716/#2846 as noted earlier.

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

Metadata

Metadata

Assignees

Labels

source/creatorFiled by the new-issue-creator jobtask/triageQueue packet kind: verify, reproduce, and route this item

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions