Summary
CI failure rate (last 20 completed ci.yml runs): 2/20 failed (10%) · 3 cancelled · 15 success. No consecutive-failure streak (failures are isolated, one run apart from healthy runs). Recommended action: monitor — failures look like isolated test flakiness, not a regression, but the rate sits right at the 10% threshold so it's worth tracking over the next few days.
Failure Details
Runs inspected:
- Run 34554365689 (2026-09-11T02:22Z) —
failure
- Run 34532163744 (2026-09-10T21:26Z) —
failure
- (3
cancelled runs, not treated as failures)
Failure patterns (top 2):
TestPRTransferGitIntegrationScopesPatchAndCommitMessage (pkg/cli, run 34554365689) — fails via a t.TempDir() cleanup error: unlinkat .../remote.git: directory not empty. This is a test-teardown race (leftover git objects/locks), not an assertion failure — classic flaky-test signature, not a code regression.
TestRunGraderFromStdin (pkg/cli, run 34532163744) — fails with grader timed out after 7s. Timing-sensitive test hitting its timeout under CI load — also flaky rather than a consistent/repeatable failure.
Both failures are in different tests within the same package (pkg/cli) but do not share a root cause or repeat across multiple runs, so this does not indicate an active regression — it reads as normal CI flakiness (tempdir cleanup race + timeout-sensitive grader test).
Open regression/bug issues (label: bug, regression) — top 5 open bug-labeled issues found (no issues carry both bug and regression labels currently):
None of these open issues correspond to the two flaky test failures observed above.
Generated by 🧭 Daily Regression Audit · copilot · auto · 58.6 AIC · ⌖ 6.48 AIC · ⊞ 7.1K · ◷
Summary
CI failure rate (last 20 completed
ci.ymlruns): 2/20 failed (10%) · 3 cancelled · 15 success. No consecutive-failure streak (failures are isolated, one run apart from healthy runs). Recommended action: monitor — failures look like isolated test flakiness, not a regression, but the rate sits right at the 10% threshold so it's worth tracking over the next few days.Failure Details
Runs inspected:
failurefailurecancelledruns, not treated as failures)Failure patterns (top 2):
TestPRTransferGitIntegrationScopesPatchAndCommitMessage(pkg/cli, run 34554365689) — fails via at.TempDir()cleanup error:unlinkat .../remote.git: directory not empty. This is a test-teardown race (leftover git objects/locks), not an assertion failure — classic flaky-test signature, not a code regression.TestRunGraderFromStdin(pkg/cli, run 34532163744) — fails withgrader timed out after 7s. Timing-sensitive test hitting its timeout under CI load — also flaky rather than a consistent/repeatable failure.Both failures are in different tests within the same package (
pkg/cli) but do not share a root cause or repeat across multiple runs, so this does not indicate an active regression — it reads as normal CI flakiness (tempdir cleanup race + timeout-sensitive grader test).Open regression/bug issues (label: bug, regression) — top 5 open
bug-labeled issues found (no issues carry bothbugandregressionlabels currently):require-error-code-for-github-api-throwdoes not recognizeoctokit.request()callspushSignedCommitsfallback pushes stale branch ref after rebasing detached HEADNone of these open issues correspond to the two flaky test failures observed above.