Fix M4T v2 integration tests #27911
Merged
Fix M4T v2 integration tests #27911
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
ylacombe
changed the title
ydshieh
approved these changes
Dec 8, 2023
|
OC, I've already verified that the tests pass (on a 24GB TITAN RTX)! I've also monitored by hand GPU utilization (around 10GB) so I believe it should pass on a 16GB GPU. FYI, the tests that I've changed verify that every task-specific model has a 1-to-1 correspondence with the task-agnostic model |
iantbutler01
pushed a commit
to BismuthCloud/transformers
that referenced
this pull request
Dec 16, 2023
change dtype of some integration tests
staghado
pushed a commit
to staghado/transformers
that referenced
this pull request
Jan 15, 2024
change dtype of some integration tests
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.
What does this PR do?
Some M4T-v2 integration tests are causing GPUs OOM. It happens when we load two models together. I thus shifted some integration tests to half precision which should solve the issue.
cc @ydshieh @ArthurZucker