-
-
Notifications
You must be signed in to change notification settings - Fork 719
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
Handle failing plugin.close()
calls during scheduler shutdown
#6450
Conversation
Sure. I was just being lazy. pushed up |
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.
Thanks @mrocklin. This looks like a reasonable addition. I've left a couple of nice-to-have, but not blocking comments
assert "123" in out | ||
assert "456" in out |
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.
It would also be nice to check that the logger exceptions also occurred as expected
try: | ||
await func() | ||
except Exception: | ||
logger.exception("Plugin call failed during scheduler.close") |
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.
Including the plugin name in this message would be nice because as is we just know that some plugin method failed, but not which plugin
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.
logger.exception includes the traceback which should include the plugin class name, although it could be a base class that fails
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.
Ah, thanks for pointing that out @graingert
rerun tests Note: rerunning gpuCI tests since those errors should be fixed by #6434 |
plugin.close()
calls during scheduler shutdown
No description provided.