Avoid all-zeor attnetion mask used in testing #26469
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
|
The documentation is not available anymore as the PR was closed or merged. |
blbadger
pushed a commit
to blbadger/transformers
that referenced
this pull request
Nov 8, 2023
fix Co-authored-by: ydshieh <ydshieh@users.noreply.github.com>
EduardoPach
pushed a commit
to EduardoPach/transformers
that referenced
this pull request
Nov 18, 2023
fix Co-authored-by: ydshieh <ydshieh@users.noreply.github.com>
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?
The method
random_attention_maskused in testing makes sure the last token is non-zero. However, this property will be changed if a causal mask is applied.This causes some issues in CI, see issue reported
pytorch/pytorch#110213
In general, a sequence with all zero as attention mask is bad. Let's avoid testing with such case.
(However, we probably need to do some processing in the modeling code - if torch decide this is undefined behavior and won't make change to have previous behavior).