-
Notifications
You must be signed in to change notification settings - Fork 220
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
tracking removal of the set_inductor_config
argument from quantize_
#1715
Comments
vkuzo
added a commit
that referenced
this issue
Feb 14, 2025
…tion Summary: We want to migrate this to individual workflows, see #1715 for migration plan. This PR is step 1 where we enable distinguishing whether the user specified this argument or not. After this PR, we can control the behavior per-workflow, such as setting this functionality to False for future training workflows. Test Plan: CI Reviewers: Subscribers: Tasks: Tags:
vkuzo
added a commit
that referenced
this issue
Feb 14, 2025
…tion Summary: We want to migrate this to individual workflows, see #1715 for migration plan. This PR is step 1 where we enable distinguishing whether the user specified this argument or not. After this PR, we can control the behavior per-workflow, such as setting this functionality to False for future training workflows. Test Plan: CI Reviewers: Subscribers: Tasks: Tags:
vkuzo
added a commit
that referenced
this issue
Feb 14, 2025
…tion Summary: We want to migrate this to individual workflows, see #1715 for migration plan. This PR is step 1 where we enable distinguishing whether the user specified this argument or not. After this PR, we can control the behavior per-workflow, such as setting this functionality to False for future training workflows. Test Plan: CI Reviewers: Subscribers: Tasks: Tags:
vkuzo
added a commit
that referenced
this issue
Feb 14, 2025
make quantize_.set_inductor_config None by default for future deprecation Summary: We want to migrate this to individual workflows, see #1715 for migration plan. This PR is step 1 where we enable distinguishing whether the user specified this argument or not. After this PR, we can control the behavior per-workflow, such as setting this functionality to False for future training workflows. Test Plan: CI Reviewers: Subscribers: Tasks: Tags:
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
summary
We are migrating the
set_inductor_config
argument ofquantize_
to individual workflows. Motivation:quantize_
.quantize_
API level, with individual workflows opting in as needed.API changes
The text was updated successfully, but these errors were encountered: