-
Notifications
You must be signed in to change notification settings - Fork 227
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
test: ensure proper cleanup between config tests #1373
Conversation
if (resettable) { | ||
if (_asyncHook) _asyncHook.disable() | ||
_asyncHook = asyncHook | ||
} |
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.
Is there a reason not to just always do 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.
Good question... I did so in the first iteration but I wasn't 100% sure if there were any implications of keeping a reference to this object so it couldn't be garbage collected. This way it only kept it around during testing - but it's probably irrelevant 🤷♂
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.
Fair. Approved anyway just to get the fix in. I can clean it up later. 🤔
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.
Approving just to get this fixed. I'd like to figure out at some point though if we can just always do this or find another way that's a bit cleaner. 🤔
jenkins run the tests please |
This was all the code that came out of trying to solve a weird CI related issue in #1114.
I thought it was best to submit it as a separate PR in case we want to backport it.