Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

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

Open
cowboyd opened this issue Jan 30, 2021 · 0 comments
Open

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

cowboyd opened this issue Jan 30, 2021 · 0 comments
Labels
@bigtest/cli Issues related to the `bigtest` command @bigtest/server

Comments

@cowboyd
Copy link
Member

cowboyd commented Jan 30, 2021

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.
@cowboyd cowboyd added @bigtest/server @bigtest/cli Issues related to the `bigtest` command labels Jan 30, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
@bigtest/cli Issues related to the `bigtest` command @bigtest/server
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@cowboyd