CI Testing transformers deprecations #2817
Merged
+22
−0
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
DON'T MERGE Check if/how often PEFT triggers transformers FutureWarning or DeprecationWarning by converting these warnings into failures. Note that there will be many false negatives, as transformers uses logger.warning frequently, which will not trigger a failure.
BenjaminBossan
changed the title
githubnemo
approved these changes
Oct 13, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Trigger an error on transformers
FutureWarningandDeprecationWarnings by converting them into failures. Since transformers often useslogger.warninginstead ofwarnings.warn(..., FutureWarning), also add a special handler to the transformers logger that errors when the logged message looks like it contains a deprecation warning.Note: Failing CI due to diffusers, not related to this PR.