-
Notifications
You must be signed in to change notification settings - Fork 47
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
Raise errors from run_training #151
base: main
Are you sure you want to change the base?
Conversation
Completely untested, just spitballing since I noticed that training failure doesn't break workflow tests for some reason. |
d0ff0ac
to
a1f56f3
Compare
The library shouldn't (just) print errors; it should raise errors and let callers deal with them. This patch also makes the function raise RuntimeError when training process returns a non-zero return code, or when it times out on waiting for exit. ilab cli already handles all Exceptions raised by the function. KeyboardInterrupt won't be caught by this exception handler since it's not Exception (but BaseException), but it's handled by click library instead [1]. The intent of this patch is to make `ilab train` fail with non-zero return code when training routine failed. [1] https://click.palletsprojects.com/en/7.x/exceptions/#where-are-errors-handled Signed-off-by: Ihar Hrachyshka <[email protected]>
This pull request has been automatically marked as stale because it has not had activity within 90 days. It will be automatically closed if no further activity occurs within 30 days. |
This pull request has merge conflicts that must be resolved before it can be |
No description provided.