From b51f1cb55f4d91783a424bf699baa30149616043 Mon Sep 17 00:00:00 2001 From: Dotta <34892728+cryppadotta@users.noreply.github.com> Date: Thu, 12 Nov 2026 16:35:30 -0600 Subject: [PATCH] test(chat): size the long Board publication tests' timeout to their measured work (#21205) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit ## Thinking Path > - Paperclip is the open source app people use to manage AI agents for work > - The chat-channel integration suite is one 86,000-line file. Its cases share one database, and the chat services scan that whole database > - The "Lossless long Board publications" cases publish 100,000-character messages in many durable parts. They use the file's default 15 s test timeout > - Run alone, a case takes about 0.6 s. Late in a full run of the file, the same cases take 6–10 s locally and 1.4–15 s in CI, because earlier cases leave rows that the services still scan > - On #21041, "keeps an ambiguous slack text part blocked across restart…" hit the 15 s limit twice (30 041 ms with its retry), and the GitHub variant passed at 14 960 ms > - This pull request gives this describe block a 45 s timeout, sized to the measured work > - The benefit is that the chat shard stops failing on unrelated PRs when these cases run late in a shard ## Linked Issues or Issue Description **What happened?** `server/src/__tests__/chat-channels.integration.test.ts` > "Lossless long Board publications" > "keeps an ambiguous slack text part blocked across restart and retries only that part and its tail" failed with `Test timed out in 15000ms` on PR #21041 (General tests chat 2/3), a PR that did not change chat code. It passed on rerun. **Expected behavior** The case passes wherever the shard puts it. **Steps to reproduce** Run the whole file: `cd server && npx vitest run src/__tests__/chat-channels.integration.test.ts --reporter=json`. In my local full run, "preserves all 100000 characters for slack new-comment publication" took 9 505 ms and "keeps an ambiguous slack text part…" took 5 856 ms. Run alone, they take 817 ms and 577 ms. In CI logs from the last 48 hours, the ambiguous-part cases took between 1 408 ms and over 15 000 ms. **Paperclip version or commit** master at 4e932fd178 and later. **Deployment mode** CI server tests (embedded PostgreSQL). **Agent adapter(s) involved** N/A, CI test. ## What Changed - `server/src/__tests__/chat-channels.integration.test.ts`: `describe("Lossless long Board publications", { timeout: 45_000 }, …)`. Other heavy publication cases in this file already use 40 s. ## Verification - With an injected 18 s wait in the ambiguous slack case, the case passes on this branch. On master the same wait fails at 15 s. - `npx vitest run src/__tests__/chat-channels.integration.test.ts -t "Lossless long Board publications"`: 16 of 16 pass. ## Risks - Low risk. Test-only change. A real hang in these cases now fails after 45 s instead of 15 s. - This does not fix the underlying slowdown: cases get about 10 times slower late in this file because services scan rows that earlier cases leave in the shared database. Splitting the file or giving groups their own database is the structural fix. That is larger than this PR. ## Model Used - Claude Opus 5.5 (`claude-opus-5-5`), Anthropic, in Claude Code with tool use (shell, GitHub CLI, Vitest). ## Checklist - [x] I have included a thinking path that traces from project context to this change - [x] I have specified the model used (with version and capability details) - [x] I have checked ROADMAP.md and confirmed this PR does not duplicate planned core work - [x] I have searched GitHub for duplicate or related PRs and linked them above - [x] I have either (a) linked existing issues with `Fixes: #` / `Closes #` / `Refs #` OR (b) described the issue in-PR following the relevant issue template - [x] I have not referenced internal/instance-local Paperclip issues or links (only public GitHub `#NNN` / `github.com/paperclipai/paperclip` URLs) - [x] My branch name describes the change (e.g. `docs/...`, `fix/...`) and contains no internal Paperclip ticket id or instance-derived details - [x] I have run tests locally and they pass - [x] I have added or updated tests where applicable - [x] I have updated relevant documentation to reflect my changes - [x] I have considered and documented any risks above - [ ] All Paperclip CI gates are green - [ ] Greptile is 5/5 with no open P2s, recommendations, or follow-ups - [x] I will address all Greptile and reviewer comments before requesting merge 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-authored-by: Claude Opus 5.5 --- server/src/__tests__/chat-channels.integration.test.ts | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/server/src/__tests__/chat-channels.integration.test.ts b/server/src/__tests__/chat-channels.integration.test.ts index b396659ed9a..cacb87a0d20 100644 --- a/server/src/__tests__/chat-channels.integration.test.ts +++ b/server/src/__tests__/chat-channels.integration.test.ts @@ -84333,7 +84333,7 @@ describeEmbeddedPostgres("chat channel control-plane integration", () => { ); }); - describe("Lossless long Board publications", () => { + describe("Lossless long Board publications", { timeout: 45_000 }, () => { async function longFixture( provider: "slack" | "github" | "microsoft-teams", ) {