GitHub Actions: 49 failing pytests on PyPy 3.11 #10288
Open
+5
−27
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
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #10288 +/- ##
=======================================
Coverage 95.86% 95.86%
=======================================
Files 175 175
Lines 19074 19074
=======================================
Hits 18286 18286
Misses 788 788 🚀 New features to boost your workflow:
|
cclauss
changed the title
|
🤖 According to the primer, this change has no effect on the checked open source code. 🤖🎉 This comment was generated for commit d49764d |
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.
Type of Changes
Description
Why recreate a venv and keep reactivating that venv at each job step when actions/setup-python already automatically does so?
Why keep dependencies in both pyproject.toml and multiple requirements_*.txt files which make cache key calculation complex?
Remove the complex cache gymnastics to see if pytests can pass on PyPy 3.11.
Refs #XXXX
Closes #10287
Closes #10286
The one failing pytest on PyPy3.9 and PyPy3.10 seems to be a full path vs. partial path difference.
Which is minor but the 48 other failing pytests on PyPy3.11 seem to require attention.