Skip to content

Soak, concurrency, and mid-stream failure suites #380

Description

@rainmanjam

Three gaps named in docs/notes/testing-by-area.md, parked together because each needs a harness the repo does not have yet.

Duration. The longest suite is 75 s; real broadcasts run for hours. Backoff crawl toward the 30 s ceiling, memory growth, disk fill and reconnect churn are duration bugs and nothing would currently see them.

Concurrency. N sources × M destinations is unmeasured. docs/ENCODING.md's "~4% of a core per destination" has no test behind it — unlike the rendition ladder figures, which #369 measured.

Mid-stream failure injection. acceptance-failover covers a switch; nothing covers a platform refusing at minute 30 of a healthy broadcast, a network drop, or the encoder dying mid-stream.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions