Skip to content

[CI] Keep live-api dev server alive between readiness and assertion steps #343

Description

@iPLAYCAFE-dev

Reproduction

Current next (76d43073ed82ebb1a9c0fc7e7907e8785229ed6a) and Draft PR #339 reproduce this in CI run 30290906878. A blob comparison shows #339 does not modify this gate or its inputs, so this is tracked as a next baseline failure.

Run the CI live-api job on next.

Expected

The server that passes readiness remains available to the following live API assertion step.

Actual

Readiness succeeds, then the next workflow step receives ECONNREFUSED 127.0.0.1:3000. The workflow starts bun run dev ... & in the prior step, so the background process does not survive the step boundary reliably.

Scope

Keep server startup and assertions in one supervised step, or use another explicit lifecycle mechanism that always tears down. #339 changes neither the workflow nor live API test.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions