Repository navigation
ci-job-timing: add context report and job-number lookup - #1356
Conversation
Bugbot couldn't run - usage limit reachedBugbot 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) |
Bugbot couldn't run - usage limit reachedBugbot 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) |
8bb9bc5 to
81762de
Compare
Revision history
|
Bugbot couldn't run - usage limit reachedBugbot 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) |
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com> Change-Id: I038998b8c65e8267a8a5c96bf926270df24bca7e
81762de to
3ac093f
Compare
|
@Mergifyio queue |
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
|
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
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.pyprintedRan 16 tests ... OKpython3 engine/skills/make-pr/scripts/preflight.py --base origin/main --dry-runprintedunit product-skill: 3 file(s)andok preflight passedon the stack tippython3 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.pyandcheck_no_tracked_local_artifacts.pyeach exited 0 on both commitsrun every tests/ dirstep. Blocker: it takes about 54 minutes and runs in CI on this pull requestRevert Plan
Revert Plan
git revert <sha>🤖 Generated with Claude Code