Skip to content
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

Merged
merged 5 commits into from
May 10, 2024
Merged

Fix sagemaker config #2753

merged 5 commits into from
May 10, 2024

Conversation

muellerzr
Copy link
Collaborator

@muellerzr muellerzr commented May 7, 2024

What does this PR do?

Puts enable_cpu_affinity into the SagemakerConfig and write_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) be False

Fixes #2744

Before submitting

  • This PR fixes a typo or improves the docs (you can dismiss the other checks if that's the case).
  • Did you read the contributor guideline,
    Pull Request section?
  • Was this discussed/approved via a Github issue or the forum? Please add a link
    to it if that's the case.
  • Did you make sure to update the documentation with your changes? Here are the
    documentation guidelines, and
    here are tips on formatting docstrings.
  • Did you write any new necessary tests?

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

@muellerzr
Copy link
Collaborator Author

(Will be safe to merge after the user can verify :) )

@HuggingFaceDocBuilderDev

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.

Copy link
Member

@BenjaminBossan BenjaminBossan left a 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?

@muellerzr
Copy link
Collaborator Author

@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

@muellerzr muellerzr requested review from BenjaminBossan and removed request for BenjaminBossan May 9, 2024 13:00
Copy link
Member

@BenjaminBossan BenjaminBossan left a 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.

@muellerzr muellerzr merged commit 47bb2dd into main May 10, 2024
25 checks passed
@muellerzr muellerzr deleted the fix-sagemaker branch May 10, 2024 13:09
muellerzr added a commit that referenced this pull request May 10, 2024
* Fix sagemaker

* Default to False

* Include fixes

* Nit

* Ignore launching
muellerzr added a commit that referenced this pull request May 10, 2024
* Fix sagemaker

* Default to False

* Include fixes

* Nit

* Ignore launching
@nroggendorff
Copy link

thank you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

SageMaker config stopped working in Accelerate version 0.29+
4 participants