yolo/arr
3
0
Fork 0
Code Issues 12 Pull Requests Actions Packages Projects Releases Wiki Activity

arr-api tests flake with PoolTimedOut under load #154

New Issue
Open
opened 2026-08-23 20:50:08 +01:00 by naps62-yolo · 0 comments
naps62-yolo commented 2026-08-23 20:50:08 +01:00
Owner
Copy Link
Copy Source

arr-api's roots::tests::an_unknown_kind_or_policy_is_a_422_naming_the_field
failed with sqlx PoolTimedOut during a full just ci run, cancelling the
other 369 tests. It passes in isolation in 0.07s and the retried gate was fully
green at 393/393.

The trigger was machine load — several worktrees running the gate at once, all
opening SQLite pools. scripts/gate.sh serialises whole gate runs, but nextest
still runs tests in parallel inside one, and the pool's 30s acquire timeout is
reachable when the box is busy.

Not a defect in shipped code, and not urgent. Recording it because an
unrecorded flake gets rediscovered: worth deciding whether the test pool wants a
longer acquire timeout, a smaller max connection count, or the affected tests
want serialising.

Deliberately filed with no milestone — this is test infrastructure, not TV
tracking, and should not gate that milestone.

`arr-api`'s `roots::tests::an_unknown_kind_or_policy_is_a_422_naming_the_field` failed with sqlx `PoolTimedOut` during a full `just ci` run, cancelling the other 369 tests. It passes in isolation in 0.07s and the retried gate was fully green at 393/393. The trigger was machine load — several worktrees running the gate at once, all opening SQLite pools. `scripts/gate.sh` serialises whole gate runs, but nextest still runs tests in parallel inside one, and the pool's 30s acquire timeout is reachable when the box is busy. Not a defect in shipped code, and not urgent. Recording it because an unrecorded flake gets rediscovered: worth deciding whether the test pool wants a longer acquire timeout, a smaller max connection count, or the affected tests want serialising. Deliberately filed with no milestone — this is test infrastructure, not TV tracking, and should not gate that milestone.
naps62-yolo added the area/apidifficulty/easytype/test labels 2026-08-23 20:50:08 +01:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
area/api
arr-api
 area/ci
CI and test harness
 area/compat
arr-compat
 area/core
arr-core
 area/daemon
arr-daemon
 area/db
arr-db
 area/dl
arr-dl
 area/indexer
arr-indexer
 area/infra
workspace and tooling
 area/meta
arr-meta
 area/parse
arr-parse
 area/probe
arr-probe
 area/subs
arr-subs crate: providers, extraction, translation, sync
 area/web
web/
 difficulty/easy
bounded, obvious approach, few files
 difficulty/hard
subtle correctness or cross-cutting
 difficulty/moderate
multiple files, judgement, an interface to design
 difficulty/trivial
one file, mechanical, no design decisions
 phase/1-skeleton
workspace, CI, config, database, empty API and SPA
 phase/2-logic
parsing and policy engine, pure, no network
 phase/3-sourcing
TMDB and Prowlarr, read-only
 phase/4-movies
movies end to end
 phase/5-ui
search, buckets, library views, queues
 phase/6-tv
seasons, episodes, tracking, derived status
 phase/7-people
owner tags and notifications
 phase/8-compat
Jellyseerr shim
 phase/9-subtitles
build order: subtitles, DESIGN.md §15
 type/bug
type/chore
type/feature
type/test
No Label area/api difficulty/easy type/test
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
hermes (Hermes (agent)) naps62 (Miguel Palhas) naps62-yolo (naps62-yolo (agent))
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: yolo/arr#154
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?