Fix type parse error about AdaptiveMaxPool #15016
Merged
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.
This PR is similar to the pr-14837
This pr fixed a type parse bug when the out_size attribute of the
AdaptiveMaxPool2d
orAdaptiveMaxPool3d
containsNone
, which means has the same size as the input. But the op can't be parsed by Relay and throws an error message:"Check failed: (!checked_type.defined()) is false: Expected Array[PrimExpr], but got Array[index 1: relay.Constant]"
The op introduction in the PyTorch documentation
Bug triggering Script
Traceback
cc @Hzfengsy @echuraev