test: give the 10k-iteration sort-key property test its own timeout #318

Merged

fable-5 merged 1 commits from fix/sort-key-test-timeout into main 2026-08-02 14:30:05 +02:00

Conversation 0 Commits 1 Files Changed 1 +46 -38

fable-5 commented 2026-08-02 14:01:32 +02:00

Collaborator

Copy Link

What

Give the 10.000-iteration sort-key property test an explicit 30 s timeout instead of the 5000 ms default.

Why

Under parallel CI load this test has repeatedly exceeded the default per-test timeout - run 685 (on main) and run 699 (on #317), both on 2026-08-01, with the identical, unchanged test passing on rerun 702. This is the documented runner signature (single-test timeout under parallel load), not a functional regression: locally the test finishes in ~1.3 s, so 30 s is generous headroom rather than a mask for a real slowdown.

Deliberately kept out of #307, where it did not belong.

Notes

• Prettier re-indented the test body one level because the it(...) call now spans multiple arguments - no functional change beyond the timeout option and the doc comment.
• Full api suite against a fresh DB: 106 files, 598 passed / 13 skipped.

## What Give the 10.000-iteration sort-key property test an explicit 30 s timeout instead of the 5000 ms default. ## Why Under parallel CI load this test has repeatedly exceeded the default per-test timeout - run 685 (on `main`) and run 699 (on #317), both on 2026-08-01, with the identical, unchanged test passing on rerun 702. This is the documented runner signature (single-test timeout under parallel load), not a functional regression: locally the test finishes in ~1.3 s, so 30 s is generous headroom rather than a mask for a real slowdown. Deliberately kept out of #307, where it did not belong. ## Notes - Prettier re-indented the test body one level because the `it(...)` call now spans multiple arguments - no functional change beyond the timeout option and the doc comment. - Full api suite against a fresh DB: 106 files, 598 passed / 13 skipped.

fable-5 added 1 commit 2026-08-02 14:01:32 +02:00

test: give the 10k-iteration sort-key property test its own timeout ... 78258c4f9b

Under parallel CI load the test repeatedly exceeded the default 5000 ms
per-test timeout (run 685 on main, run 699 on an unrelated PR); the
identical test passed on rerun. Locally it finishes in about 1.3 s, so
30 s is generous headroom, not a mask for a regression.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_017aviRTgWCcAHUh1SBoxf6P

fable-5 merged commit 78258c4f9b into main 2026-08-02 14:30:05 +02:00

Sign in to join this conversation.

Reviewers

No reviewers

Labels

Clear labels   

area:auth

  

area:docs

  

area:export

  

area:ops

  

area:storage

  

area:supply-chain

  

auth

Authentication, permissions, quotas

  

backend

API server (apps/api)

  

blocked

Blocked on external dependency/infrastructure

  

collab

Collaboration server (apps/collab)

  

deployment

Docker, CI/CD, hosting

  

docs

Documentation

  

effort:L

  

effort:M

  

effort:S

  

frontend

SPA (apps/web)

  

plugins

Plugin system and SDK

  

qa

Tests, fixtures, e2e

  

vs-nfd

  

vs-nfd:blocker

No Label

area:auth

area:docs

area:export

area:ops

area:storage

area:supply-chain

auth

backend

blocked

collab

deployment

docs

effort:L

effort:M

effort:S

frontend

plugins

qa

vs-nfd

vs-nfd:blocker

Milestone

Clear milestone

No items

No Milestone

Projects

Clear projects

No project

Assignees

Clear assignees

No Assignees

1 Participants

Notifications

Subscribe

Due Date

The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: stwaidele/dorfteich#318

No description provided.