Skip to content

ci: cap job runtimes in id and mcpx workflows - #294

Closed
dezren39 wants to merge 1 commit into
mainfrom
fix/job-timeout-caps
Closed

dezren39 wants to merge 1 commit into
mainfrom
fix/job-timeout-caps

Conversation

@dezren39

@dezren39 dezren39 commented Oct 18, 2026 •

Copy link
Copy Markdown
Member

What

Adds job-level timeout-minutes caps to the two longest-running workflows in this repo:

  • .github/workflows/id-check.yml — check job (nix flake check): 60 minutes. This workflow is the ~116-minute-average PR gate; its worst observed failing leg ran 37 minutes, so 60 is generous headroom for a healthy run while bounding the known LogSync hang (Bulk LogSync test retries a mid-stream reset instead of explaining it #241) instead of letting it run to the 360-minute platform default.
  • .github/workflows/mcpx.yml — build job: 30 minutes (observed workflow max 11.3 minutes).

YAML-only change; no steps, triggers, or job logic touched.

Tracking

Part of #293 (timeout caps for all jobs in all workflows). This PR covers only the two super-long offenders; the remaining workflows in this repo stay with #293.


View with [code]smith Autofix with [code]smith
Need help on this PR? Tag @codesmith-bot with what you need.

Summary by CodeRabbit

  • Chores
    • Automated checks and build processes now have defined time limits, preventing them from running indefinitely. These behind-the-scenes adjustments do not change product features or behavior. No end-user-facing changes are included in this update.

@dezren39
dezren39 requested a review from a team as a code owner October 18, 2026 15:40
@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Oct 18, 2026 •

Copy link
Copy Markdown

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review ✅ Completed 2026-10-18T15:41:37.209018Z 2654f25 PR opened
ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

@coderabbitai

coderabbitai Bot commented Oct 18, 2026 •

Copy link
Copy Markdown

Review in Change Stack →

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration
  • Configuration used: defaults
  • Review profile: CHILL
  • Plan: Advanced
  • Run ID: 6466d1f9-c9b4-4451-b99a-32cddbacbe84
📥 Commits

Reviewing files that changed from the base of the PR and between 60f7a63 and 2654f25.

📒 Files selected for processing: 2
  • .github/workflows/id-check.yml
  • .github/workflows/mcpx.yml

Included review availability: This review used your included allowance. Your plan provides up to 10 included reviews per hour; 3 remain after this review.

📝 Walkthrough

The check job in id-check.yml now has a 60-minute timeout. The build job in mcpx.yml now has a 30-minute timeout.

Changes: Workflow job timeouts

Layer / File(s) Summary
Set job timeout limits
.github/workflows/id-check.yml, .github/workflows/mcpx.yml
The check job has a 60-minute timeout. The build job has a 30-minute timeout.

Priority: ⬇️ Low

Estimated code review effort: 1 (Trivial) | ~5 minutes

Change: Other

Merge Risk: ⚪ Minimal · up to 2654f

The ID check and MCPX build now have runtime limits. Available evidence does not establish that either limit interrupts a healthy run, so no concrete merge-blocking risk is established.

### Architecture Summary

Architecture risk: 🔵 Low · up to 2654f

The changed surface does not map to a changed system, dependency edge, entrypoint, or external dependency.

Changed systems: None identified.

Architecture concerns
No architecture-level concerns identified.

Review details

Before / after behavior

  • observed — Modified behavior in .github/workflows/id-check.yml: Sets the check job timeout to 60 minutes.
  • observed — Modified behavior in .github/workflows/mcpx.yml: Adds a 30-minute timeout to the build job.
Pre-merge checks: Passed 5
Check name Status Explanation
Description Check Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check Passed The title clearly and concisely describes the main change: adding runtime caps to the ID and MCPX CI workflows.
Docstring Coverage Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0…
Linked Issues check Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check Passed Check skipped because no linked issues were found for this pull request.
Full details: Docstring Coverage

Explanation

No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0 files. (2 skipped: 2 unsupported.)

✨ Finishing Touches: 💡 1
🧪 Generate unit tests (beta)
  • Commit to this branch
  • Create a new PR
🛠️ Fix failing CI checks: 💡
  • Commit to this branch
  • Create a new PR
  • Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Comment @coderabbitai help to get the list of available commands.

dezren39 pushed a commit that referenced this pull request Oct 18, 2026
The build job compiled the same code twice: direct-toolchain tests
(~4.6 min) and then a full nix build (~5.4 min), ~10.6 min total.
The PR/push path is now one direct-Go job (setup-go cache made
explicit); vendorHash repair keeps working as its own bot-only job,
the one step that genuinely needs nix. The flake is still evaluated
on every PR by nix-ci.

Includes the 30-minute job cap from #294. Refs #286.
dezren39 pushed a commit that referenced this pull request Oct 18, 2026
id-check ran the full nix flake check on every PR (~116 min avg):
the Playwright E2E and NixOS VM checks were most of it. The PR gate
now builds the fast checks explicitly (unit + integration tests,
lint, format, typecheck, doc, crash gate) behind magic-nix-cache so
unchanged derivations are not rebuilt from a cold store. The full
flake check — E2E and VM tests included — runs nightly and on
demand in the new id-e2e-nightly workflow.

Includes the 60-minute job cap from #294. Refs #292, #288.
@dezren39

Copy link
Copy Markdown
Member Author

Superseded by PR #295 (merged 1b2ed38), which carries these same timeout caps inside the mcpx/id restructure (id jobs 60 min, mcpx jobs 30 min) plus the prettier blank-line fix this PR was blocked on. Closing without merging.

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant