-
Notifications
You must be signed in to change notification settings - Fork 695
pytorch/audio/ import cleanup #3702
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
base: main
Are you sure you want to change the base?
Conversation
🔗 Helpful Links🧪 See artifacts and rendered test results at hud.pytorch.org/pr/pytorch/audio/3702
Note: Links to docs will display an error until the docs builds have been completed. ❌ 2 New FailuresAs of commit 1d6fc9d with merge base ccd78ff ( NEW FAILURES - The following jobs have failed:
This comment was automatically generated by Dr. CI and updates every 15 minutes. |
This pull request was exported from Phabricator. Differential Revision: D51316163 |
Summary: import cleanup under fbcode//pytorch/audio/ Differential Revision: D51316163
36d21d2
to
1d6fc9d
Compare
This pull request was exported from Phabricator. Differential Revision: D51316163 |
@@ -5,7 +5,6 @@ | |||
|
|||
|
|||
def base_smoke_test(): | |||
import torchaudio # noqa: F401 |
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.
Please do not change this. This script is for OSS testing, and this line is checking if the extension is properly configured.
Hi @azad-meta! Thank you for your pull request. We require contributors to sign our Contributor License Agreement, and yours needs attention. You currently have a record in our system, but the CLA is no longer valid, and will need to be resubmitted. ProcessIn order for us to review and merge your suggested changes, please sign at https://code.facebook.com/cla. If you are contributing on behalf of someone else (eg your employer), the individual CLA may not be sufficient and your employer may need to sign the corporate CLA. Once the CLA is signed, our tooling will perform checks and validations. Afterwards, the pull request will be tagged with If you have received this in error or have any questions, please contact us at cla@meta.com. Thanks! |
Differential Revision: D51316163