-
Notifications
You must be signed in to change notification settings - Fork 1.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Tool] add pynose-1.4.8 to replace nose #48812
Merged
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
* `nose` is too old to compatible with python3.10+ nose-devs/nose#1122 * turn to pynose to fix the compatibility issue https://pypi.org/project/pynose/1.4.8/#description Signed-off-by: Kevin Xiaohua Cai <[email protected]>
alvin-celerdata
approved these changes
Jul 23, 2024
[FE Incremental Coverage Report]✅ pass : 0 / 0 (0%) |
[BE Incremental Coverage Report]✅ pass : 0 / 0 (0%) |
@Mergifyio backport branch-3.3 branch-3.2 branch-3.1 |
✅ Backports have been created
|
mergify bot
pushed a commit
that referenced
this pull request
Jul 24, 2024
* `nose` is too old to compatible with python3.10+ nose-devs/nose#1122 * turn to pynose to fix the compatibility issue https://pypi.org/project/pynose/1.4.8/#description Signed-off-by: Kevin Xiaohua Cai <[email protected]> (cherry picked from commit 97d861f)
mergify bot
pushed a commit
that referenced
this pull request
Jul 24, 2024
* `nose` is too old to compatible with python3.10+ nose-devs/nose#1122 * turn to pynose to fix the compatibility issue https://pypi.org/project/pynose/1.4.8/#description Signed-off-by: Kevin Xiaohua Cai <[email protected]> (cherry picked from commit 97d861f)
mergify bot
pushed a commit
that referenced
this pull request
Jul 24, 2024
* `nose` is too old to compatible with python3.10+ nose-devs/nose#1122 * turn to pynose to fix the compatibility issue https://pypi.org/project/pynose/1.4.8/#description Signed-off-by: Kevin Xiaohua Cai <[email protected]> (cherry picked from commit 97d861f)
This was referenced Jul 24, 2024
wanpengfei-git
pushed a commit
that referenced
this pull request
Jul 24, 2024
Co-authored-by: Kevin Cai <[email protected]>
wanpengfei-git
pushed a commit
that referenced
this pull request
Jul 24, 2024
Co-authored-by: Kevin Cai <[email protected]>
wanpengfei-git
pushed a commit
that referenced
this pull request
Jul 24, 2024
Co-authored-by: Kevin Cai <[email protected]>
dujijun007
pushed a commit
to dujijun007/starrocks
that referenced
this pull request
Jul 29, 2024
* `nose` is too old to compatible with python3.10+ nose-devs/nose#1122 * turn to pynose to fix the compatibility issue https://pypi.org/project/pynose/1.4.8/#description Signed-off-by: Kevin Xiaohua Cai <[email protected]>
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.
nose
is too old to compatible with python3.10+ Change in Python3.10 from collections.Callable to collections.abc.Callable nose-devs/nose#1122Why I'm doing:
What I'm doing:
Fixes #issue
What type of PR is this:
Does this PR entail a change in behavior?
If yes, please specify the type of change:
Checklist:
Bugfix cherry-pick branch check: