Uh oh!
There was an error while loading.Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork1.2k
[ci] Fix PyPy venv caching issue#10392
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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
Uh oh!
There was an error while loading.Please reload this page.
Conversation
codecovbot commentedMay 18, 2025 • edited
Loading Uh oh!
There was an error while loading.Please reload this page.
edited
Uh oh!
There was an error while loading.Please reload this page.
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@## main #10392 +/- ##==========================================+ Coverage 95.84% 95.90% +0.05%========================================== Files 174 176 +2 Lines 18995 19122 +127 ==========================================+ Hits 18206 18339 +133+ Misses 789 783 -6 🚀 New features to boost your workflow:
|
🤖 According to the primer, this change hasno effect on the checked open source code. 🤖🎉 This comment was generated for commit03eaced |
Pierre-Sassoulas left a comment
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.
Amazing catch, it's been bothering me since pypy 3.11 was added 😄 (should we wait for the fix un setup-python or should we add cdce8p to the trusted workflow ? It feels like it enlarge the surface of attack)
cdce8p commentedMay 18, 2025 • edited
Loading Uh oh!
There was an error while loading.Please reload this page.
edited
Uh oh!
There was an error while loading.Please reload this page.
Does it increase the surface area though? It's my own fork and I have full access anyway. Yes, we could wait for the PR but the Github action staff can be slow to respond sometimes unfortunately. Might be worth it to unblock our CI in the meantime by adding |
Pierre-Sassoulas commentedMay 18, 2025
No you're right if your account is compromised it's already game over |
58813cd intopylint-dev:mainUh oh!
There was an error while loading.Please reload this page.
ghost commentedMay 18, 2025
The backport to To backport manually, run these commands in your terminal: # Fetch latest updates from GitHubgit fetch# Create a new working treegit worktree add .worktrees/backport-maintenance/3.3.x maintenance/3.3.x# Navigate to the new working treecd .worktrees/backport-maintenance/3.3.x# Create a new branchgit switch --create backport-10392-to-maintenance/3.3.x# Cherry-pick the merged commit of this pull request and resolve the conflictsgit cherry-pick -x --mainline 1 58813cd3627194395f6c0c893b217fb71cc425a3# Push it to GitHubgit push --set-upstream origin backport-10392-to-maintenance/3.3.x# Go back to the original working treecd ../..# Delete the working treegit worktree remove .worktrees/backport-maintenance/3.3.x Then, create a pull request where the |
cdce8p commentedMay 18, 2025
Let's not backport this one. The CI for the maintenance branch is fine without it. |
The
testsjob uses thepython-versionoutput fromactions/setup-pythonas part of the cache key. That works well for cpython, however is broken for PyPy which doesn't include the Python version itself. Thus the workflow currently restores the first cached venv, e.g.pypy-3.11onpypy-3.10, and thus no packages are actually available.The current key prefix for PyPy (3.10 and 3.11):
Linux-pypy7.3.19-venv-.... Better would beLinux-pypy3.10.16-7.3.19-venv-.../Linux-pypy3.11.11-7.3.19-venv-....This isn't an issue on our backport branch since PyPy 3.9 was dropped recently and so the PyPy versions are actually different. Nevertheless it might be good to backport it as well.
IMO this is really an issue with the
setup-pythonaction. Opened an issue and PR upstream.actions/setup-python#1109
actions/setup-python#1110
To unblock our workflow, I created a custom tag with just the fix.
https://github.com/cdce8p/setup-python/compare/v5.6.0...v5.6.0-c1