Segformer tests fix #40725
Closed
Segformer tests fix #40725
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
- Remove temporary 'tatus' file containing git diff - Add templates/** to ruff exclude list to avoid template syntax errors - Fix F402 errors: rename loop variables to avoid shadowing imports - Fix F841 errors: remove unused variable assignments - Fix F401 errors: remove unused imports (except intentional availability checks) - All critical F errors resolved, only 4 false positive F401 errors remain in benchmark files
- Update SegformerMixFFN copy in src/transformers/models/glpn/modeling_glpn.py - This resolves the check_copies.py failure in CircleCI consistency checks
|
[For maintainers] Suggested jobs to run (before merge) run-slow: glpn, segformer |
|
Special prize for a copilot PR where you also committed your OpenSSH private key ⭐ |
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 # (issue)
Before submitting
Pull Request section?
to it if that's the case.
documentation guidelines, and
here are tips on formatting docstrings.
Who can review?
Anyone in the community is free to review the PR once the tests have passed. Feel free to tag
members/contributors who may be interested in your PR.