-
Notifications
You must be signed in to change notification settings - Fork 633
Add test when there are no segments #12646
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
Conversation
🔗 Helpful Links🧪 See artifacts and rendered test results at hud.pytorch.org/pr/pytorch/executorch/12646
Note: Links to docs will display an error until the docs builds have been completed. ❌ 2 New Failures, 1 Unrelated FailureAs of commit 4197bc2 with merge base c9df2aa ( NEW FAILURES - The following jobs have failed:
FLAKY - The following job failed but was likely due to flakiness present on trunk:
This comment was automatically generated by Dr. CI and updates every 15 minutes. |
This pull request was exported from Phabricator. Differential Revision: D78568839 |
This PR needs a
|
Summary: The deprecation warning should only appear when there are values inside the constant_buffer and nothing inside the constant_segment. Even when there are no constants in the program, we expect to have one 'segment' storing the placeholder for non-constants. Fix failing jobs caused by error logging from pytorch#12295 Test failures: https://hud.pytorch.org/pr/pytorch/executorch/12631#46239138027 Arm test is using a recently-generated PTE, however hitting the deprecation warning because the pte has no constants. Differential Revision: D78568839
This pull request was exported from Phabricator. Differential Revision: D78568839 |
runtime/executor/program.cpp
Outdated
// https://github.com/pytorch/executorch/issues. | ||
ET_LOG( | ||
Error, | ||
"!!DEPRECATED!! This branch is deprecated from ExecuTorch 0.7; re-export this PTE file to ensure support on newer runtimes."); |
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.
Nit: can we explain a bit more in the error message, and perhaps how to mitigate it? Seems like one has to read code to get around this error.
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.
I previously had a longer message, but this caused errors in internal tests where they have a limit of 128 bytes for the log string - see D77965467
Summary: The deprecation warning should only appear when there are values inside the constant_buffer and nothing inside the constant_segment. Even when there are no constants in the program, we expect to have one 'segment' storing the placeholder for non-constants. Fix failing jobs caused by error logging from pytorch#12295 Test failures: https://hud.pytorch.org/pr/pytorch/executorch/12631#46239138027 Arm test is using a recently-generated PTE, however hitting the deprecation warning because the pte has no constants. Differential Revision: D78568839
This pull request was exported from Phabricator. Differential Revision: D78568839 |
Summary: The deprecation warning should only appear when there are values inside the constant_buffer and nothing inside the constant_segment. Even when there are no constants in the program, we expect to have one 'DataSegment' storing the placeholder for non-constants. Fix failing jobs caused by error logging from pytorch#12295 Test failures: https://hud.pytorch.org/pr/pytorch/executorch/12631#46239138027 Arm test is using a recently-generated PTE, however hitting the deprecation warning because the pte has no constants. Reviewed By: larryliu0820 Differential Revision: D78568839
This pull request was exported from Phabricator. Differential Revision: D78568839 |
Summary: The deprecation warning should only appear when there are values inside the constant_buffer and nothing inside the constant_segment. Even when there are no constants in the program, we expect to have one 'DataSegment' storing the placeholder for non-constants. Move this into the 'if' branch. Fix failing jobs caused by error logging from pytorch#12295 Test failures: https://hud.pytorch.org/pr/pytorch/executorch/12631#46239138027 Arm test is using a recently-generated PTE, however hitting the deprecation warning because the pte has no constants. Reviewed By: larryliu0820 Differential Revision: D78568839
This pull request was exported from Phabricator. Differential Revision: D78568839 |
@pytorchbot cherry-pick --onto release/0.7 -c {release; add log for deprecated feature} |
❌ 🤖 pytorchbot command failed:
Try |
@pytorchbot cherry-pick --onto release/0.7 -c {release} |
❌ 🤖 pytorchbot command failed:
Try |
@pytorchbot cherry-pick --onto release/0.7 -c release |
Cherry picking #12646The cherry pick PR is at #12687 The following tracker issues are updated: Details for Dev Infra teamRaised by workflow job |
Differential Revision: D78568839 Pull Request resolved: pytorch#12646
Summary:
The deprecation warning should only appear when there are values inside the constant_buffer and nothing inside the constant_segment.
Even when there are no constants in the program, we expect to have one 'segment' storing the placeholder for non-constants.
Fix failing jobs caused by error logging from #12295
Test failures: https://hud.pytorch.org/pr/pytorch/executorch/12631#46239138027
Arm test is using a recently-generated PTE, however hitting the deprecation warning because the pte has no constants.
Differential Revision: D78568839