Summary
- CI failure rate (last 20 runs): 15% (3/20 failed, 4/20 cancelled, 13/20 succeeded)
- Consecutive failure streak: none — failures are isolated, interspersed with successful runs
- Recommended action: monitor (failure rate is above the 10% healthy threshold but shows a single repeating pattern, not a broad regression)
Failure Details
Failed runs analyzed (most recent 3):
| Run ID |
Created |
Title |
| 33923818265 |
2026-09-04T22:02:58Z |
Handle GitHub reaction rate limits gracefully (#58610) |
| 33921888966 |
2026-09-04T21:36:40Z |
Expose Linear and Jira tools in safe-output prompts (#58599) |
| 33920010431 |
2026-09-04T21:12:38Z |
CI |
Top failure pattern:
js-integration-live-api job failing consistently — this job failed in all 3 recent failed runs, the single common denominator across otherwise unrelated PRs. This strongly suggests a shared/flaky dependency (e.g. a live external API integration test) rather than per-PR regressions, since the PRs touch unrelated areas (reaction rate limits, Linear/Jira tool exposure, and a plain CI push).- Run 33921888966 additionally failed on
Integration Add with dispatch-workflow Dependencies, a second job, indicating this run had multiple concurrent issues (possibly infra-related, e.g. rate limiting or transient network failures during live API calls).
- Direct job log tail retrieval was not available (
get_job_logs reported "unknown method" and list_workflow_jobs/get_workflow_run_logs_url only exposed job/run metadata and a downloadable log ZIP rather than inline tail output), so failure messages could not be extracted verbatim in this run. The job-name pattern above was derived from list_workflow_jobs conclusions across the 3 failed runs.
Open regression/bug issues (label: bug, regression):
Recommendation: Investigate the js-integration-live-api job for flakiness/rate-limiting against its live API dependency; consider adding retry logic or mocking if it continues to fail across unrelated PRs.
Generated by 🧭 Daily Regression Audit · copilot · auto · 45.9 AIC · ⌖ 5.15 AIC · ⊞ 6.8K · ◷
Summary
Failure Details
Failed runs analyzed (most recent 3):
Top failure pattern:
js-integration-live-apijob failing consistently — this job failed in all 3 recent failed runs, the single common denominator across otherwise unrelated PRs. This strongly suggests a shared/flaky dependency (e.g. a live external API integration test) rather than per-PR regressions, since the PRs touch unrelated areas (reaction rate limits, Linear/Jira tool exposure, and a plain CI push).Integration Add with dispatch-workflow Dependencies, a second job, indicating this run had multiple concurrent issues (possibly infra-related, e.g. rate limiting or transient network failures during live API calls).get_job_logsreported "unknown method" andlist_workflow_jobs/get_workflow_run_logs_urlonly exposed job/run metadata and a downloadable log ZIP rather than inline tail output), so failure messages could not be extracted verbatim in this run. The job-name pattern above was derived fromlist_workflow_jobsconclusions across the 3 failed runs.Open regression/bug issues (label: bug, regression):
bugandregressionlabels via search. A broaderbug-label search surfaced unrelated open issues (repo-memory: ignore disallowed files before artifact upload and push #58119 repo-memory artifact filtering, Failure to create PR due to merge conflict #56567 PR merge-conflict failure) but none tagged specifically for CI regressions.Recommendation: Investigate the
js-integration-live-apijob for flakiness/rate-limiting against its live API dependency; consider adding retry logic or mocking if it continues to fail across unrelated PRs.