This repository was archived by the owner on Sep 10, 2025. It is now read-only.
Fix device mismatch bug in T5 implementation #1944
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.
Error
Fix & Context
relative_bucketsis a Tensor created without specifying device, meaning it automatically gets put on CPU; however, the rest of the input Tensors are created with CUDA; therefore, there is a mismatch when attempting to do an arithmetic operation. Discovered when working on AI for CS workflow.Testing
Fluent2 and Bento notebook; passes existing tests here. Do we have any Integration tests w/ CUDA we could run in OSS to check this?