Skip to content

test: give the 202-turn chat room test 30 seconds - #81

Merged
cardmagic merged 1 commit into
mainfrom
test/chat-room-timeout
Oct 18, 2026
Merged

cardmagic merged 1 commit into
mainfrom
test/chat-room-timeout

Conversation

@cardmagic

Copy link
Copy Markdown
Owner

Summary

CI on the 1.0.3 merge commit (run 39142558596) failed in the quality job. The test "keeps the text of a pinned message after newer messages push it out" ran for 5568 ms, and the default limit is 5000 ms.

The test makes 202 durable turns in order: one pin and 200 posts, each a SQLite commit. It takes about 0.5 seconds locally, with or without coverage. In the quality job, 81 test files run in parallel under coverage on a shared runner, so the test ran about 10 times slower. The change gives this one test a 30 second limit, as test/effect-recovery.test.ts and test/instance-retention.test.ts do for their durable work.

Checks

  • pnpm run check passes.
  • test/compare-chat-room.test.ts passes.

The pinned message test makes 202 durable turns in order. It takes
about half a second on a laptop, but CI on the 1.0.3 merge commit took
5.6 seconds in the quality job, where 81 test files run in parallel
under coverage, and the default 5 second limit failed the run. Other
tests with this much durable work set their own limit.
@greptile-apps

greptile-apps Bot commented Oct 18, 2026 •

Copy link
Copy Markdown

RetriggerView in GreptileConfidence Score: 5/5

[Low impact] This PR appears safe to merge.

Summary

Gives the pinned-message test 30 seconds to finish instead of the default 5 seconds.

  • The pinned-message test can run for up to 30 seconds.

Reviews (1) · Last reviewed commit: "test: give the 202-turn chat room test 3..." · Reviewed by Greptile

@cardmagic
cardmagic merged commit d224e23 into main Oct 18, 2026
20 checks passed
@cardmagic
cardmagic deleted the test/chat-room-timeout branch October 18, 2026 16:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant