Skip to content

ci-job-timing: add context report and job-number lookup - #1356

Merged
mergify[bot] merged 1 commit into
mainfrom
stack/EdbertChan/cjt-3-context/ci-job-timing-add-context-report-job-num-lookup--038998b8
Oct 13, 2026
Merged

mergify[bot] merged 1 commit into
mainfrom
stack/EdbertChan/cjt-3-context/ci-job-timing-add-context-report-job-num-lookup--038998b8

Conversation

@EdbertChan

@EdbertChan EdbertChan commented Oct 12, 2026 •

Copy link
Copy Markdown
Owner

Summary

A CI job sometimes starts late, and the step report cannot say why. This adds a second report that shows what the job waits for.

It lists the jobs that must finish first and counts which one finished last. It also shows the gap between that finish and the job starting.

It can start from known job numbers, so it no longer has to scan many pipelines to find the right ones.

Review Claim

Approve a read-only report that explains why a CI job started late, using GitLab data.

Review Lane

behavior

Review Unit

product-skill

Safety Invariant

It only reads Datadog and GitLab. The token comes from the environment and is never printed or saved.

Slice Rationale

This builds on the first report and shares its file, so it stacks on top. The job-number lookup is a small follow-up to the same report and rides along.

Non-goals

  • No analysis of flags against run time.
  • No speed-up model.
  • No change to the step table.
  • No writes to GitLab or Datadog.

Measured

none: this adds a new report and nothing existing to compare against

Test Plan

Test Plan
  • python3 -m unittest product/skills/ci-job-timing/tests/test_ci_job_timing.py printed Ran 16 tests ... OK
  • python3 engine/skills/make-pr/scripts/preflight.py --base origin/main --dry-run printed unit product-skill: 3 file(s) and ok preflight passed on the stack tip
  • python3 scripts/ci/check_skills_registry.py, check_skills_three_harnesses.py, check_ecosystem_boundaries.py, check_skill_file_refs.py, check_skill_test_coverage.py --base origin/main --head HEAD, check_skill_test_debt_no_growth.py, check_skill_trigger_mechanism.py, check_no_dated_provenance.py --base origin/main, check_no_new_comments.py --base origin/main, check_hook_test_coverage.py, check_no_silent_hook_except.py, check_rules_are_wired.py and check_no_tracked_local_artifacts.py each exited 0 on both commits
  • Not run: the full run every tests/ dir step. Blocker: it takes about 54 minutes and runs in CI on this pull request
  • Not run: a live run against GitLab for a real job. Blocker: it needs a GitLab token, which this slice did not use
  • Fixture vs live: the tests above use fixtures only; no live side effect was exercised

Revert Plan

Revert Plan
  • Safe to revert? Yes
  • Revert command: git revert <sha>
  • Post-revert steps: None
  • Data migration? No

🤖 Generated with Claude Code

@EdbertChan
EdbertChan added this pull request to stack #1357 October 12, 2026 19:30
@cursor

cursor Bot commented Oct 12, 2026

Copy link
Copy Markdown

Bugbot couldn't run - usage limit reached

Bugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit.

A user or team admin can review and increase usage limits in the Cursor dashboard.

(requestId: 01007f33-871a-4339-bd69-4c5a40bc1150)

@EdbertChan EdbertChan changed the title ci-job-timing: add context report and job-number lookup Add a report that explains why a CI job started late Oct 12, 2026
@cursor

cursor Bot commented Oct 12, 2026

Copy link
Copy Markdown

Bugbot couldn't run - usage limit reached

Bugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit.

A user or team admin can review and increase usage limits in the Cursor dashboard.

(requestId: 7fb5deff-6734-4bbd-83c3-4a7438b4e8bb)

@EdbertChan
EdbertChan removed this pull request from stack #1357 October 13, 2026 04:06
@EdbertChan
EdbertChan changed the base branch from stack/EdbertChan/cjt-3-context/register-ci-job-timing-skills-toml--0226f357 to main October 13, 2026 04:06
@EdbertChan
EdbertChan force-pushed the stack/EdbertChan/cjt-3-context/ci-job-timing-add-context-report-job-num-lookup--038998b8 branch from 8bb9bc5 to 81762de Compare October 13, 2026 04:06
@EdbertChan EdbertChan changed the title Add a report that explains why a CI job started late ci-job-timing: add context report and job-number lookup Oct 13, 2026
@EdbertChan
EdbertChan changed the base branch from main to stack/EdbertChan/cjt-3-context/add-ci-job-timing-skill-per-step-timing-report--d0dec928 October 13, 2026 04:06
@EdbertChan

Copy link
Copy Markdown
Owner Author

Revision history

# Type Changes Reason Date
1 initial 8bb9bc5 2026-10-13 04:06 UTC
2 unknown 8bb9bc5 → 81762de 2026-10-13 04:06 UTC

@EdbertChan
EdbertChan added this pull request to stack #1375 October 13, 2026 04:06
@cursor

cursor Bot commented Oct 13, 2026

Copy link
Copy Markdown

Bugbot couldn't run - usage limit reached

Bugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit.

A user or team admin can review and increase usage limits in the Cursor dashboard.

(requestId: 772b713d-53c0-4d4a-8c84-923e5dc08474)

Base automatically changed from stack/EdbertChan/cjt-3-context/add-ci-job-timing-skill-per-step-timing-report--d0dec928 to main October 13, 2026 05:51
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Change-Id: I038998b8c65e8267a8a5c96bf926270df24bca7e
@mergify
mergify Bot force-pushed the stack/EdbertChan/cjt-3-context/ci-job-timing-add-context-report-job-num-lookup--038998b8 branch from 81762de to 3ac093f Compare October 13, 2026 05:51
@EdbertChan

Copy link
Copy Markdown
Owner Author

@Mergifyio queue

@mergify

mergify Bot commented Oct 13, 2026 •

Copy link
Copy Markdown
Contributor

Merge Queue Status

This pull request spent 1 hour 7 minutes 59 seconds in the queue, including 49 minutes 23 seconds running CI.

Required conditions to merge

@mergify mergify Bot added the queued label Oct 13, 2026
@mergify
mergify Bot merged commit 7ede769 into main Oct 13, 2026
4 checks passed
@mergify mergify Bot removed the queued label Oct 13, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant