Skip pypi transformers until release #1911
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
| @@ -26,8 +26,8 @@ jobs: | |||
| strategy: | |||
| fail-fast: false | |||
| matrix: | |||
| # Add pypi back in after the next release! | |||
There was a problem hiding this comment.
Just a suggestion: Do we want to use a format like # TODO (transformers v4.33) Add pypi back in after the next release! to comments that are tied to a specific version?
There was a problem hiding this comment.
Good idea! I'll make the tweak in a bit :)
BenjaminBossan
approved these changes
Aug 31, 2023
|
The documentation is not available anymore as the PR was closed or merged. |
5 tasks
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?
This PR in transformers (huggingface/transformers#25077) makes the pypi version of transformers incompatible with the git-version of the tests. As a result, this PR skips their integration tests (but keeps github). Will be re-added in the next release.
Fixes # (issue)
Failing merge tests
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.
@BenjaminBossan