Switch deberta to use the "int" dtype #1315
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 will be int32 on jax and torch, but int64 on tf, which is what we need for proper accelerator support
mattdangerw
force-pushed
the
deberta-int-dtype
branch
from
f4712da to
ccad751
Compare
|
Hmm these test failures look unrelated to this change, but instead some recent keras-nightly changes. Will take a look. |
|
/gcbrun |
mattdangerw
added a commit
to mattdangerw/keras-hub
that referenced
this pull request
Dec 7, 2023
This will be int32 on jax and torch, but int64 on tf, which is what we need for proper accelerator support
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.
This will be int32 on jax and torch, but int64 on tf, which is what we need for proper accelerator support