-
Notifications
You must be signed in to change notification settings - Fork 325
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
Work around legacy integration test resource leak. #4244
Work around legacy integration test resource leak. #4244
Conversation
fd4c26e
to
7c9b16e
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Shouldn't we find the resource leak instead of patching it like this?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I guess this is fine, since these tests are legacy and maybe they will go away at some point.
022a333
to
2b95d6d
Compare
This reverts commit a72c70a. (it turns out this only helps with resource consumption because after running the first bach of tests, defaultMainWithIngredients exits... m|
This reverts commit a72c70a. (it turns out this only helps with resource consumption because after running the first bach of tests, defaultMainWithIngredients exits... m|
Checklist
Add a new entry in an appropriate subdirectory ofchangelog.d