Skip to content

ci: 10 most-recent failed runs analysed — all fixes exist in open PRs, action needed to merge #37

@erudenko

Description

@erudenko

CI Failure Audit — 2026-04-13

This issue was generated by the CI maintenance agent after reviewing the 10 most-recent failed GitHub Actions runs. All failures are real (not transient), all fixes already exist in open PRs, and no new fix branches were required.


The 10 Failed Runs

Run ID Workflow Branch Commit Triggered by
24307096245 Test Stats Plugin fix/ci-all-fixes-final 84411b6d intermediate commit
24307096246 Test Plugins fix/ci-all-fixes-final 84411b6d intermediate commit
24307087724 Test Plugins fix/ci-all-fixes-final c12a54cf intermediate commit
24306967746 Test Plugins fix/ci-all-fixes-final ea72ec07 intermediate commit
24306950584 Test Plugins fix/ci-all-fixes-final e3d5e8dc intermediate commit
24306895086 Test Stats Plugin fix/ci-all-fixes-final b6de79a2 intermediate commit
24306895101 Test Plugins fix/ci-all-fixes-final b6de79a2 intermediate commit
24298790076 Test Stats Plugin fix/ci-workflow-trigger-broadening 6f38db63 PR #32 HEAD
24298790072 Test Plugins fix/ci-workflow-trigger-broadening 6f38db63 PR #32 HEAD
24298782547 Test Stats Plugin fix/ci-workflow-trigger-broadening 6f38db63 PR #32 HEAD

Root Causes (all 4 addressed in existing PRs)

1. Unused TypeScript imports (TS6133)

tsc --noEmit fails under noUnusedLocals for three imports left behind after refactors:

  • conventions-integration.test.ts: removeGitignoreEntries
  • doctor.test.ts: vi
  • conventions-manager.ts: existsSync

2. Stale hardcoded test dates

plugins/stats/tests/db.test.ts and integration.test.ts used the hardcoded date "2026-03-26" which is now >17 days old — outside the 7-day and 14-day rolling query windows used by getSessionSummary, getTopTools, and getDurationTrend.

3. browser-use version mismatch in marketplace.json

plugins/browser-use/plugin.json is at v1.1.2 but .claude-plugin/marketplace.json was left at v1.1.1, causing the marketplace-sync integration test to fail.

4. Hardcoded branch filters in workflow triggers

test-plugins.yml and test-stats.yml had branches: [main, fix/ci-type-errors-and-stale-test-date] allowlists, making CI invisible to all other branches.


Current State of Fix PRs

PR Branch CI at HEAD Fixes covers Recommendation
#34 fix/ci-all-fixes-final ✅ SUCCESS All 4 root causes Merge
#33 fix/ci-consolidated ✅ SUCCESS All 4 root causes Merge (alternative to #34)
#24 fix/ci-24065489776-ts-and-dates ✅ SUCCESS Root causes 1–3 Merge or close if #33/#34 merged first
#32 fix/ci-workflow-trigger-broadening ❌ FAILING Root cause 4 only (inherits broken base) Close — superseded by #33/#34
#31 fix/ci-main-browser-use-version No runs Root cause 3 only (targets main dist-orphan) Close — no CI can run there
#28 fix/ci-24276607217-browser-use-version N/A Root cause 3 only Close — superseded by #24
#23 fix/ci-typescript-and-stats-dates-resolved N/A (was invisible) Root causes 1–2 only Close — superseded by #24
#22 fix/ci-typescript-and-stats-dates N/A (was invisible) Root causes 1–2 only Close — superseded by #23/#24

Recommended Actions

  1. Merge PR fix(ci): consolidated — TS imports, stale dates, browser-use version, unrestricted triggers #33 or PR fix(ci): complete all-fixes branch — rolling stats dates in integration.test.ts + browser-use 1.1.2 #34 — either one resolves all outstanding failures. Both have green CI on both Test Stats Plugin and Test Plugins.
  2. Close PRs fix(ci): remove unused TS imports + fix stale stats test dates #22, fix(ci): resolve merge conflict — unused TS imports + stale stats test dates #23, fix(marketplace): bump browser-use version 1.1.1 → 1.1.2 in marketplace.json #28, fix(marketplace): bump browser-use version 1.1.1 → 1.1.2 to fix CI #31, fix(ci): remove hardcoded branch filters from workflow triggers #32 — all superseded; keeping them open adds confusion and merge-conflict risk.
  3. After merging, the base branch fix/ci-type-errors-and-stale-test-date will also become green (its current HEAD failures are what the fix PRs address).

Why No New Fix Branch Was Created

All 10 failed runs are from intermediate/stale commits on branches where the HEAD is already green, or from a branch that is fully superseded by an open PR with green CI. Creating a new fix/ci-<run-id> branch would duplicate work that already exists. The bottleneck is review and merge, not code.

Generated by CI maintenance agent on 2026-04-13

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions