CI Failure Details
CI Run: https://github.com/coder/coder/actions/runs/25428928667
Failed Job: https://github.com/coder/coder/actions/runs/25428928667/job/74589773311 (test-go-pg (ubuntu-latest))
Commit: a74015fc85cb121d828336126e1e4af7368973c4 (Cian Johnston)
Date: 2026-05-06
Failing Package
github.com/coder/coder/v2/aibridge/internal/integrationtest
Error Output
FAIL
FAIL github.com/coder/coder/v2/aibridge/internal/integrationtest 2.720s
Error Analysis
The job log reports a package-level failure for aibridge/internal/integrationtest without any --- FAIL: lines or subtest names. No build errors or panics were printed in the log segment surrounding the failure, so the specific test case that failed is currently unknown.
No data race warnings, panics, or OOM indicators were observed in the job log.
Root Cause Assessment
Flaky integration test (unknown subtest). The package failed during CI on ubuntu-latest, but the logs did not include a specific failing test name or assertion details.
Assignment Analysis
I could not run git blame on the failing test because the test name was not emitted in the logs. Using package-level history as a fallback:
git log --oneline -10 aibridge/internal/integrationtest
# dbb50eba feat: remove 429 from aibridge circuit breaker failure conditions (Susana Ferreira)
# a24dc19d chore: clean up env var usage in aibridge (Paweł Banaszewski)
Assigning to @ssncferreira as the most recent maintainer of this integration test package.
Related Issues
Reproduction
go test ./aibridge/internal/integrationtest -count=1
CI Failure Details
CI Run: https://github.com/coder/coder/actions/runs/25428928667
Failed Job: https://github.com/coder/coder/actions/runs/25428928667/job/74589773311 (test-go-pg (ubuntu-latest))
Commit: a74015fc85cb121d828336126e1e4af7368973c4 (Cian Johnston)
Date: 2026-05-06
Failing Package
github.com/coder/coder/v2/aibridge/internal/integrationtestError Output
Error Analysis
The job log reports a package-level failure for
aibridge/internal/integrationtestwithout any--- FAIL:lines or subtest names. No build errors or panics were printed in the log segment surrounding the failure, so the specific test case that failed is currently unknown.No data race warnings, panics, or OOM indicators were observed in the job log.
Root Cause Assessment
Flaky integration test (unknown subtest). The package failed during CI on ubuntu-latest, but the logs did not include a specific failing test name or assertion details.
Assignment Analysis
I could not run
git blameon the failing test because the test name was not emitted in the logs. Using package-level history as a fallback:Assigning to @ssncferreira as the most recent maintainer of this integration test package.
Related Issues
Reproduction