flake: TestAgent_Startup/HomeDirectory
@mafredri is already working on this.
Since Jun 12, 2026.
Assessment
This issue has not been assessed yet.
Description
CI Failure Details
CI Run: https://github.com/coder/coder/actions/runs/27441018780
Failed Job: https://github.com/coder/coder/actions/runs/27441018780/job/81114905940 (test-go-pg (windows-2022))
Commit: d6aa3d61ee4ad38b60d887641ff8084f4b676c2b (TJ) https://github.com/coder/coder/commit/d6aa3d61ee4ad38b60d887641ff8084f4b676c2b
Failing Test
TestAgent_Startup/HomeDirectory
File: agent/agent_test.go (around line ~2249)
Error Output (panic / timeout)
=== FAIL: agent (0.00s)
panic: test timed out after 20m0s
running tests:
TestAgent_Startup/HomeDirectory (19m57s)
Error Analysis
The agent package hit the Go test watchdog timeout on Windows. The running test list shows TestAgent_Startup/HomeDirectory stuck for ~20 minutes, indicating a hang in startup/manifest resolution or agent setup on Windows.
Root Cause Assessment
Process timeout / hang in TestAgent_Startup/HomeDirectory on Windows CI.
Data Race / OOM Checks
Searched logs for WARNING: DATA RACE, out of memory, signal: killed — none found. Failure is a Go test timeout panic.
Assignment Analysis
Intended blame command:
git blame -L 2242,2275 agent/agent_test.go
Proxy via history (available tooling):
git log --oneline -10 --follow agent/agent_test.go- Most recent substantive change touching this area:
3955df79("fix(agent): unify working directory resolution") by Mathias Fredriksson.
- Most recent substantive change touching this area:
Assigning to @mafredri as the most recent modifier of the working directory resolution + startup test area.
Related Issues
Searched coder/internal for:
TestAgent_Startup/TestAgent_Startup/HomeDirectoryagent_test.go+Startuptest timed out after 20m+agent
No matching issues found.
Reproduction
go test ./agent -run TestAgent_Startup/HomeDirectory -count=1
- Dominant language
- No language data
- Stars
- 3
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from coder/internal
-
flake
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 4/5 3-5 days Newbie friendliness 45/100
-
flake
-
flake