You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Recommended action: Investigate — failure rate is well above the 10% healthy threshold, and one failure pattern (a Go test panic/failure) is a genuine code regression rather than infrastructure flakiness.
Failure Details
Runs analyzed (most recent 20, ci.yml, status=completed): run numbers 55080–55111, spanning 2026‐09‐14 00:47–19:12 UTC. All on main.
The test fails because a temp directory for a cached workflow run already exists — indicating the test doesn't clean up prior state or there's a caching/dedup bug in pkg/cli/logs_cached_json_live_integration_test.go:57. This is a consistent failure, not flaky infra — worth a dedicated fix.
go mod download failed: stream error: stream ID 639; INTERNAL_ERROR; received from peer fetching github.com/thlib/go-timezone-local@v0.0.8 from proxy.golang.org (Integration Add Workflows job).
install-shellcheck failed: curl: (22) The requested URL returned error: 504 downloading from github.com/koalaman/shellcheck releases, after 3 retries (ShellCheck job).
Workflow lock file drift check failed: ERROR: Workflow lock files are out of sync with their markdown sources (run [aw] Issue Arborist failed #55107, "Check workflow markdown/lock drift" job) — likely a race where a markdown workflow was updated without gh aw compile being run in the same commit, rather than a code regression.
Flaky vs. consistent: The go mod/shellcheck download failures and lock-drift issue appear as one-off/transient (network 504s, timing/commit-ordering), while the TestLogsCachedJSONLLiveCaching directory-exists failure looks like a reproducible logic bug worth triaging.
Open regression/bug issues (labels: bug, regression, state: open, top 5):
(4 additional matching issues exist but were withheld from this report due to an integrity/visibility restriction on those specific issues)
No new regression issue was found directly tied to the TestLogsCachedJSONLLiveCaching failure pattern above; consider filing one if it recurs in subsequent runs.
Summary
ci.yml): 7/20 = 35%--max-tokensflag for claude CLI #55095)Failure Details
Runs analyzed (most recent 20,
ci.yml,status=completed): run numbers 55080–55111, spanning 2026‐09‐14 00:47–19:12 UTC. All onmain.Failed runs: #55107, #55100, #55099, #55095, #55094, #55092, #55080
Top failure patterns identified (from 3 most recent failed runs, job-level logs):
Genuine regression — flaky/broken test cleanup in
TestLogsCachedJSONLLiveCaching(run [WIP] [test-parallel] Daily Go Test Parallelizer: work in progress #55099, job "Integration: CLI Logs Live Cache"):The test fails because a temp directory for a cached workflow run already exists — indicating the test doesn't clean up prior state or there's a caching/dedup bug in
pkg/cli/logs_cached_json_live_integration_test.go:57. This is a consistent failure, not flaky infra — worth a dedicated fix.Infra flakiness — network transient errors (runs [daily issues] Daily Issues Report - 2026-08-23 #55100, [aw] Issue Arborist failed #55107):
go mod downloadfailed:stream error: stream ID 639; INTERNAL_ERROR; received from peerfetchinggithub.com/thlib/go-timezone-local@v0.0.8from proxy.golang.org (Integration Add Workflows job).install-shellcheckfailed:curl: (22) The requested URL returned error: 504downloading fromgithub.com/koalaman/shellcheckreleases, after 3 retries (ShellCheck job).ERROR: Workflow lock files are out of sync with their markdown sources(run [aw] Issue Arborist failed #55107, "Check workflow markdown/lock drift" job) — likely a race where a markdown workflow was updated withoutgh aw compilebeing run in the same commit, rather than a code regression.Flaky vs. consistent: The
go mod/shellcheckdownload failures and lock-drift issue appear as one-off/transient (network 504s, timing/commit-ordering), while theTestLogsCachedJSONLLiveCachingdirectory-exists failure looks like a reproducible logic bug worth triaging.Open regression/bug issues (
labels: bug, regression,state: open, top 5):No new regression issue was found directly tied to the
TestLogsCachedJSONLLiveCachingfailure pattern above; consider filing one if it recurs in subsequent runs.