You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Setting to use torch dynamo compiling path in eager (#2045)
Summary:
Pull Request resolved: #2045
1/ Refactoring to use is_torchdynamo_compiling() from torchrec.pt2.checks instead of code duplication
2/ We have alternative path of logic is_torchdynamo_compiling(). Our tests are not testing it without compilation, so it is error prone to not catch some shape mismatch or etc. =>
We need a tool how to cover it with eager tests without compilation. =>
Introducing global setting to force using is_torchdynamo_compiling() path for eager for test coverage and debug.
Enabling this path for test_pt2_multiprocess, that first eager iteration will be done on is_torchdynamo_compiling path.
Reviewed By: PaulZhang12, gnahzg
Differential Revision: D57860075
0 commit comments