-
Notifications
You must be signed in to change notification settings - Fork 976
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
Fix sagemaker config #2753
Fix sagemaker config #2753
Conversation
(Will be safe to merge after the user can verify :) ) |
The docs for this PR live here. All of your documentation changes will be reflected on that endpoint. The docs are available until 30 days after the last update. |
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.
Puts enable_cpu_affinity down a level so sagemaker can work.
Not quite sure what that means, but if the user can confirm that this fixes the issue, it should be good. However, it looks like the new test is failing because it requires sagemaker to be installed, can you verify?
@BenjaminBossan updated. Will also re-look at the test to make sure it doesn't need to be ran per-se, just check for config validity |
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, LGTM, tests seem to be running correctly.
* Fix sagemaker * Default to False * Include fixes * Nit * Ignore launching
* Fix sagemaker * Default to False * Include fixes * Nit * Ignore launching
thank you! |
What does this PR do?
Puts
enable_cpu_affinity
into theSagemakerConfig
andwrite_basic_config
(Similar to debug)We already have checks to verify if we should call cpu_affinity, so its safe to do (and will default to
False
if they didn't pass it in), so even if sagemaker doesn't support it it will still (almost always) beFalse
Fixes #2744
Before submitting
Pull Request section?
to it if that's the case.
documentation guidelines, and
here are tips on formatting docstrings.
Who can review?
Anyone in the community is free to review the PR once the tests have passed. Feel free to tag
members/contributors who may be interested in your PR.
@BenjaminBossan