-
Notifications
You must be signed in to change notification settings - Fork 516
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
Prune xfail e2e LTC tests & fix bugs from functionalization pass #1044
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This commit fixes some bugs that previously caused tests to fail and get marked xfail. * Created function to recursively move TorchScriptValue to a new device * Fixed bug in HistogramBinningCalibrationByFeature test where constant tensor in constructor wasn't properly defined as a buffer, which caused a device mismatch
silvasean
approved these changes
Jul 12, 2022
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.
Awesome!
python/torch_mlir_e2e_test/torchscript/configs/lazy_tensor_core.py
Outdated
Show resolved
Hide resolved
henrytwo
added a commit
that referenced
this pull request
Jul 12, 2022
- Pruned number of xfailed e2e LTC tests from 305 to 134 - Reviewed every failure to ensure the error genuinely warrants an xfail - Fixed bug where non-tensor outputs of LTC computation had `.to('cpu')` called, which caused a failure and inflated the xfail count - Fixed bug with `HBC_basic` test where a constant tensor was created in its constructor without being declared as a buffer, which prevented the device from being updated when the parent `torch.nn.Module` got moved to the `lazy` device - Note that this test is still xfail'd due to some unsupported ops. Left a comment about some potential issues that may arise if it gets reenabled in the future - Updated autogen `GeneratedTorchOps.td` to reflect the latest set of supported ops - Renamed `aten.zero.functionalization` to `aten.zero` to reflect upstream PyTorch changes
antoniojkim
pushed a commit
that referenced
this pull request
Jul 15, 2022
- Pruned number of xfailed e2e LTC tests from 305 to 134 - Reviewed every failure to ensure the error genuinely warrants an xfail - Fixed bug where non-tensor outputs of LTC computation had `.to('cpu')` called, which caused a failure and inflated the xfail count - Fixed bug with `HBC_basic` test where a constant tensor was created in its constructor without being declared as a buffer, which prevented the device from being updated when the parent `torch.nn.Module` got moved to the `lazy` device - Note that this test is still xfail'd due to some unsupported ops. Left a comment about some potential issues that may arise if it gets reenabled in the future - Updated autogen `GeneratedTorchOps.td` to reflect the latest set of supported ops - Renamed `aten.zero.functionalization` to `aten.zero` to reflect upstream PyTorch changes
antoniojkim
pushed a commit
that referenced
this pull request
Jul 19, 2022
- Pruned number of xfailed e2e LTC tests from 305 to 134 - Reviewed every failure to ensure the error genuinely warrants an xfail - Fixed bug where non-tensor outputs of LTC computation had `.to('cpu')` called, which caused a failure and inflated the xfail count - Fixed bug with `HBC_basic` test where a constant tensor was created in its constructor without being declared as a buffer, which prevented the device from being updated when the parent `torch.nn.Module` got moved to the `lazy` device - Note that this test is still xfail'd due to some unsupported ops. Left a comment about some potential issues that may arise if it gets reenabled in the future - Updated autogen `GeneratedTorchOps.td` to reflect the latest set of supported ops - Renamed `aten.zero.functionalization` to `aten.zero` to reflect upstream PyTorch changes
antoniojkim
pushed a commit
that referenced
this pull request
Jul 22, 2022
- Pruned number of xfailed e2e LTC tests from 305 to 134 - Reviewed every failure to ensure the error genuinely warrants an xfail - Fixed bug where non-tensor outputs of LTC computation had `.to('cpu')` called, which caused a failure and inflated the xfail count - Fixed bug with `HBC_basic` test where a constant tensor was created in its constructor without being declared as a buffer, which prevented the device from being updated when the parent `torch.nn.Module` got moved to the `lazy` device - Note that this test is still xfail'd due to some unsupported ops. Left a comment about some potential issues that may arise if it gets reenabled in the future - Updated autogen `GeneratedTorchOps.td` to reflect the latest set of supported ops - Renamed `aten.zero.functionalization` to `aten.zero` to reflect upstream PyTorch changes
henrytwo
added a commit
that referenced
this pull request
Jul 29, 2022
- Pruned number of xfailed e2e LTC tests from 305 to 134 - Reviewed every failure to ensure the error genuinely warrants an xfail - Fixed bug where non-tensor outputs of LTC computation had `.to('cpu')` called, which caused a failure and inflated the xfail count - Fixed bug with `HBC_basic` test where a constant tensor was created in its constructor without being declared as a buffer, which prevented the device from being updated when the parent `torch.nn.Module` got moved to the `lazy` device - Note that this test is still xfail'd due to some unsupported ops. Left a comment about some potential issues that may arise if it gets reenabled in the future - Updated autogen `GeneratedTorchOps.td` to reflect the latest set of supported ops - Renamed `aten.zero.functionalization` to `aten.zero` to reflect upstream PyTorch changes
henrytwo
added a commit
that referenced
this pull request
Jul 29, 2022
- Pruned number of xfailed e2e LTC tests from 305 to 134 - Reviewed every failure to ensure the error genuinely warrants an xfail - Fixed bug where non-tensor outputs of LTC computation had `.to('cpu')` called, which caused a failure and inflated the xfail count - Fixed bug with `HBC_basic` test where a constant tensor was created in its constructor without being declared as a buffer, which prevented the device from being updated when the parent `torch.nn.Module` got moved to the `lazy` device - Note that this test is still xfail'd due to some unsupported ops. Left a comment about some potential issues that may arise if it gets reenabled in the future - Updated autogen `GeneratedTorchOps.td` to reflect the latest set of supported ops - Renamed `aten.zero.functionalization` to `aten.zero` to reflect upstream PyTorch changes
henrytwo
added a commit
that referenced
this pull request
Jul 30, 2022
- Pruned number of xfailed e2e LTC tests from 305 to 134 - Reviewed every failure to ensure the error genuinely warrants an xfail - Fixed bug where non-tensor outputs of LTC computation had `.to('cpu')` called, which caused a failure and inflated the xfail count - Fixed bug with `HBC_basic` test where a constant tensor was created in its constructor without being declared as a buffer, which prevented the device from being updated when the parent `torch.nn.Module` got moved to the `lazy` device - Note that this test is still xfail'd due to some unsupported ops. Left a comment about some potential issues that may arise if it gets reenabled in the future - Updated autogen `GeneratedTorchOps.td` to reflect the latest set of supported ops - Renamed `aten.zero.functionalization` to `aten.zero` to reflect upstream PyTorch changes
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Changes:
.to('cpu')
called, which caused a failure and inflated the xfail countHBC_basic
test where a constant tensor was created in its constructor without being declared as a buffer, which prevented the device from being updated when the parenttorch.nn.Module
got moved to thelazy
deviceGeneratedTorchOps.td
to reflect the latest set of supported opsaten.zero.functionalization
toaten.zero
to reflect upstream PyTorch changescc: @ke1337 @antoniojkim