Skip to content

[BUGFIX] Properly detect failure to launch process#21

Merged
aiharos merged 2 commits intohaproxytech:masterfrom
pierresouchay:detect_missing_executables_or_error_launching_program
Apr 15, 2020
Merged

[BUGFIX] Properly detect failure to launch process#21
aiharos merged 2 commits intohaproxytech:masterfrom
pierresouchay:detect_missing_executables_or_error_launching_program

Conversation

@pierresouchay
Copy link
Copy Markdown
Collaborator

In order to properly detect dataplaneapi/haproxy not launching, cmd.Process != nil needs to be checked as documented in Go APIs.

In order to properly detect dataplaneapi/haproxy not launching,
cmd.Process != nil needs to be checked as documented in Go APIs.
@pierresouchay pierresouchay force-pushed the detect_missing_executables_or_error_launching_program branch from f078623 to 99208a8 Compare April 14, 2020 16:59
pierresouchay added a commit to pierresouchay/haproxy-consul-connect that referenced this pull request Apr 14, 2020
In case where the Process dataplaneapi was not activated for instance
the process was hanging forever.

Combined with haproxytech#21
it will stop the test immediately if dataplaneapi or haproxy are not in the
path
@pierresouchay pierresouchay added bug Something isn't working criteo labels Apr 14, 2020
@aiharos aiharos merged commit 9a3e4ec into haproxytech:master Apr 15, 2020
@pierresouchay pierresouchay deleted the detect_missing_executables_or_error_launching_program branch April 15, 2020 10:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug Something isn't working criteo

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants