-
Notifications
You must be signed in to change notification settings - Fork 5.8k
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
[tune] Fix Pausing and Error Propogation #2815
Conversation
Can you also change the smoke test iterations for the pbt test to something like 20? That catches the bug and also runs reasonably fast. |
Test PASSed. |
Test PASSed. |
Test PASSed. |
@joyyoj Can you take a look please? |
Test FAILed. |
jenkins retest this please |
Test FAILed. |
Jenkins retest this please |
Test PASSed. |
the changes make sense. |
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.
lgtm based on tests and @joyyoj 's approval (I did not look carefully at the unpause crash, it looks complicated)
One minor suggestion on the error handling that might give a cleaner interface.
""" | ||
raise NotImplementedError("Subclasses of TrialExecutor must provide " | ||
"fetch_one_result() method") | ||
raise NotImplementedError |
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.
So one other way of doing this is to have fetch_one_result() return an exception object for the result if there is an error. This avoids having a separate call just for this error handling.
Merging now since this is a fairly severe regression. Comments can be done in a follow-up... |
What do these changes do?
Addresses #2814 and #2810.
ray.get
.Related issue number
Above.