CI Failure Details
CI Run: https://github.com/coder/coder/actions/runs/24098533542
Failed Job: https://github.com/coder/coder/actions/runs/24098533542/job/70305199296 (test-go-pg (ubuntu-latest))
Commit: 08bd9e672a728b3a6dc34bd9f9be13be46a630d3 (Jon Ayers)
Date: 2026-04-07
Failing Test
TestExecutorAutostartOK in coderd/autobuild/lifecycle_executor_test.go
Error Output
Error Trace: /home/runner/work/coder/coder/coderd/autobuild/lifecycle_executor_test.go:76
Error: "map[]" should have 1 item(s), but has 0
Test: TestExecutorAutostartOK
Error Trace: /home/runner/work/coder/coder/coderd/autobuild/lifecycle_executor_test.go:77
Error: map[uuid.UUID]database.WorkspaceTransition{} does not contain uuid.UUID{...}
Test: TestExecutorAutostartOK
Error Trace: /home/runner/work/coder/coder/coderd/autobuild/lifecycle_executor_test.go:78
Error: Not equal:
expected: "start"
actual : ""
Test: TestExecutorAutostartOK
Error Trace: /home/runner/work/coder/coder/coderd/autobuild/lifecycle_executor_test.go:81
Error: Not equal:
expected: "autostart"
actual : "initiator"
Test: TestExecutorAutostartOK
Root Cause Analysis
Likely flaky timing in autobuild lifecycle executor stats collection. The test expects a single transition and autostart build reason, but stats are empty and the latest build reason is initiator. This suggests the executor tick completes before the autostart transition is recorded or is racing with provisioner state/LastSeenAt updates.
No data race warnings, panics, or OOM indicators in logs.
Assignment Analysis
git blame is not available via current tooling, so used recent file history:
git log --oneline -10 --follow coderd/autobuild/lifecycle_executor_test.go
# 974ca3ed fix: use "idle timeout" as task auto-pause reason (DanielleMaywood)
# 31c12792 feat: notify on task auto pause, manual pause and manual resume (DanielleMaywood)
Most recent meaningful changes to this test file are by DanielleMaywood, so assigning to them for triage.
Related Issues
No direct match found. Similar-but-different flakes:
Reproduction
Not deterministic; appears timing-dependent in CI.
CI Failure Details
CI Run: https://github.com/coder/coder/actions/runs/24098533542
Failed Job: https://github.com/coder/coder/actions/runs/24098533542/job/70305199296 (test-go-pg (ubuntu-latest))
Commit: 08bd9e672a728b3a6dc34bd9f9be13be46a630d3 (Jon Ayers)
Date: 2026-04-07
Failing Test
TestExecutorAutostartOKincoderd/autobuild/lifecycle_executor_test.goError Output
Root Cause Analysis
Likely flaky timing in autobuild lifecycle executor stats collection. The test expects a single transition and autostart build reason, but stats are empty and the latest build reason is
initiator. This suggests the executor tick completes before the autostart transition is recorded or is racing with provisioner state/LastSeenAt updates.No data race warnings, panics, or OOM indicators in logs.
Assignment Analysis
git blameis not available via current tooling, so used recent file history:Most recent meaningful changes to this test file are by DanielleMaywood, so assigning to them for triage.
Related Issues
No direct match found. Similar-but-different flakes:
TestExecutorAutostartSkipsWhenNoProvisionersAvailable#909 (same test family, different failure)Reproduction
Not deterministic; appears timing-dependent in CI.