flake: TestInterruptAutoPromotionIgnoresLaterUsageLimitIncrease

[flake-investigator]

CI Run: https://github.com/coder/coder/actions/runs/23172387510
Failed Job: test-go-pg (ubuntu-latest)
Commit: 1031da9738a22cc7158f7b3e02e31933e7771243 (author: Michael Suchacz)

Failure:

=== FAIL: coderd/chatd TestInterruptAutoPromotionIgnoresLaterUsageLimitIncrease (0.52s)
    chatd_test.go:884:
        Error Trace: /home/runner/work/coder/coder/coderd/chatd/chatd_test.go:884
        Error:       Should be true

Observed context (from logs):

• The failure occurs right after SendMessage with content "later queued"; the test expects laterQueuedResult.Queued to be true.
• Logs show chat processing and pubsub events, then the assertion failure (no panic/OOM/race output).

Suspected root cause: Flaky test (timing-sensitive). The test assumes the chat remains busy/interrupting when the second SendMessage is called; if the chat finishes processing earlier, laterQueuedResult.Queued can be false, causing the assertion failure.

Assignment analysis:

• git log --oneline -10 --follow coderd/chatd/chatd_test.go (approximated via API list commits for the file) shows recent changes touching this test file, including:
  • 5d0eb772 "fix(cored): fix flaky TestInterruptAutoPromotionIgnoresLaterUsageLimitIncrease" by Michael Suchacz
• This commit is directly related to the test and prior flake fix; assigning to @ibetitsmike.

Related issues search (coder/internal):

• "TestInterruptAutoPromotionIgnoresLaterUsageLimitIncrease"
• "chatd_test.go" "coderd/chatd"
• "chat interrupted" pubsub
• "AutoPromotion" OR "usage limit" chatd
  No existing issues found.

Reproduction (if needed):

go test ./coderd/chatd -run TestInterruptAutoPromotionIgnoresLaterUsageLimitIncrease -count=1

Notes:

• No data race warnings, panic traces, or OOM indicators found in the job logs.

[flake-investigator]

New occurrence:

• CI Run: https://github.com/coder/coder/actions/runs/23268724218
• Failed Job: test-go-pg-17
• Commit: a6856320f96a3af76a4a86f896d5262f7dc5f61d (author: greg-the-coder)

Failure:

=== FAIL: coderd/chatd TestInterruptAutoPromotionIgnoresLaterUsageLimitIncrease (0.67s)
    chatd_test.go:984:
        Error Trace: /home/runner/work/coder/coder/coderd/chatd/chatd_test.go:984
        Error:       Should be true

Observed context:

• Pubsub/chat processing logs show the interrupt/queueing path, then the assertion fails on laterQueuedResult.Queued being false.
• No data race warnings, panic traces, or OOM indicators found in logs.

Repro:

go test ./coderd/chatd -run TestInterruptAutoPromotionIgnoresLaterUsageLimitIncrease -count=1

[flake-investigator]

New occurrence:

• CI run: https://github.com/coder/coder/actions/runs/23343011152 (job: test-go-pg (ubuntu-latest))
• Commit: 41e15ae440cc6e8a2429a44dcf57b7e603566d0a (author: Mathias Fredriksson)

Failure excerpt:

=== FAIL: coderd/chatd TestInterruptAutoPromotionIgnoresLaterUsageLimitIncrease (25.52s)
    chatd_test.go:1065:
        Error Trace: /home/runner/work/coder/coder/coderd/chatd/chatd_test.go:1065
        Error:       Condition never satisfied

No data race warnings, panic traces, or OOM indicators in the job logs.