[ROCm] add exact_dtype=False to bfloat16 test#38381
[ROCm] add exact_dtype=False to bfloat16 test#38381jeffdaily wants to merge 1 commit intopytorch:masterfrom
Conversation
ezyang
left a comment
There was a problem hiding this comment.
Please condition these on being ROCm. And you should fix these bugs eventually!
|
Actually since this unbreaks CI I'm going to land it. Please do the follow up though. |
facebook-github-bot
left a comment
There was a problem hiding this comment.
@ezyang is landing this pull request. If you are a Facebook employee, you can view this diff on Phabricator.
|
@ezyang After discussion with @rohithkrn, we need some clarification. We don’t know if it’s truly a bug, the test does computation in float32 and uses it as reference to compare against bfloat16 computation. How is this handled in other tests, if any? Also, these tests are marked |
|
Oh, if the tests are ROCm only, then non-exact is fine. No follow up needed! |
Summary: CC rohithkrn ezyang xw285cornell Fixes - TestNNDeviceTypeCUDA.test_activations_bfloat16_cuda - TestNNDeviceTypeCUDA.test_pooling_bfloat16_cuda - TestNNDeviceTypeCUDA.test_softmax_bfloat16_cuda Pull Request resolved: pytorch#38381 Differential Revision: D21549636 Pulled By: ezyang fbshipit-source-id: acb290c57eff4077b040a696267ecde613f0a433
CC @rohithkrn @ezyang @xw285cornell
Fixes