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.

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

Testing runnerv2service without command.SetEnvDumpCommandForTesting results in fork bomp #730

Open
adambabik opened this issue Jan 19, 2025 · 0 comments

Comments

@adambabik
Copy link
Collaborator

adambabik commented Jan 19, 2025

Running runnerv2service tests without the following fragment:

func init() {
	command.SetEnvDumpCommandForTesting()
}

results in fork bomb.

The goal of this issue is to understand exactly what happens and try to write a more bullet proof code so that forgetting this call in init() does not destroy the local environment.

This problem was discovered in #727.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant