Skip to content

Whenever there is a rogue process lying around, the ci command hangs rather than erroring out. #802

Open

Description

@cowboyd

As part of the diagnosis of #800, we encountered a complicating issue where the CI process would hang, while the server process would start up fine and could have tests run against it.

If the orchestrator fails to start as part of the CI command because there is an port that is unreleased, then the CI command should bark loudly.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions