Exclude MViT from cuda tests #6573
Merged
Conversation
This file contains hidden or 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
jdsgomes
approved these changes
Sep 13, 2022
facebook-github-bot
pushed a commit
that referenced
this pull request
Sep 15, 2022
Reviewed By: jdsgomes Differential Revision: D39543275 fbshipit-source-id: 200b30b2e2b317aac681402d7bb5b0eab3d0e213
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.
As noted at #6539, some variants are too big for the CUDA memory we got on the CI and occasionally fail. This is semi-random and happens from time to time. When it does, it takes down with it other models randomly (see for example maskrcnn failing as well on the linked execution).
To avoid this flakiness, we should exclude MViT from the CUDA runs.