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
Fixed CI Support with Python 3.12 #8611
Conversation
good luck and good night for today. hopefully this will be fixed tomorrow, either by you or by me or by us. |
Awesome job today @auvipy !! |
I will return to this tomorrow as well. |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #8611 +/- ##
==========================================
+ Coverage 87.24% 87.33% +0.09%
==========================================
Files 148 148
Lines 18512 18512
Branches 3109 3163 +54
==========================================
+ Hits 16150 16167 +17
+ Misses 2074 2060 -14
+ Partials 288 285 -3
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
@auvipy ready for review & merge :) |
@@ -389,12 +390,17 @@ def test_ready(self): | |||
|
|||
assert not self.app.AsyncResult(uuid()).ready() | |||
|
|||
@pytest.mark.skipif( | |||
platform.python_implementation() == "PyPy", | |||
reason="Mocking here doesn't play well with PyPy", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
TBH I'm not sure why it fails only with PyPy, but I skip it to allow us to move forward.
Not sure if it's acceptable @auvipy
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I am goin to check it in my work hours today.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think we can skip PyPy for this as the sole target of this release is to have python 3.12 compatibility!
And there are some back ends which do not play well with pypy as well. so we did skip in past as well. thanks for taking the time to figure it out! <3
@@ -75,7 +75,7 @@ jobs: | |||
strategy: | |||
fail-fast: false | |||
matrix: | |||
python-version: ['3.8', '3.9', '3.10', '3.11'] | |||
python-version: ['3.8', '3.9', '3.10', '3.11', '3.12'] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I missed it
Team Effort 💪 |
* Fixed t/unit/tasks/test_result.py::test_del() * Skip t/unit/tasks/test_result.py::test_del() if running with PyPy * Added Python 3.12 to integration tests in the CI
No description provided.