[Falcon] Fix AutoConfig Tests #26507
Closed
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 docs for this PR live here. All of your documentation changes will be reflected on that endpoint. |
|
Thanks for your PR @sanchit-gandhi! Closing in favor of #26472 |
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?
Fixes the auto-config Falcon tests that were failing on
mainafter merging #26476. Note that the latest version of the Falcon model on the Hub specifies a model type offalcon, following @Rocketknight1's Hub commit 898df13. Thus, we update the config tests intransformersto reflect this.There are still config tests to check that
trust_remote_codegives the correct configs for older versions (with specific commit ids):transformers/tests/models/falcon/test_modeling_falcon.py
Line 603 in 0b192de