Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

[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

Merged
Pierre-Sassoulas merged 1 commit intopylint-dev:mainfromcdce8p:fix-pypy-cache
May 18, 2025

Conversation

@cdce8p
Copy link
Member

Thetests job uses thepython-version output fromactions/setup-python as 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.11 onpypy-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 thesetup-python action. 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

@cdce8pcdce8p added this to the3.3.8 milestoneMay 18, 2025
@cdce8pcdce8p added MaintenanceDiscussion or action around maintaining pylint or the dev workflow Skip news 🔇This change does not require a changelog entry backport maintenance/4.0.x labelsMay 18, 2025
@codecov
Copy link

codecovbot commentedMay 18, 2025
edited
Loading

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 95.90%. Comparing base (5fce790) to head (03eaced).
⚠️ Report is 298 commits behind head on main.

Additional details and impacted files

Impacted file tree graph

@@            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

see 5 files with indirect coverage changes

🚀 New features to boost your workflow:
  • ❄️Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@github-actions
Copy link
Contributor

🤖 According to the primer, this change hasno effect on the checked open source code. 🤖🎉

This comment was generated for commit03eaced

Copy link
Member

@Pierre-SassoulasPierre-Sassoulas left a 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
Copy link
MemberAuthor

cdce8p commentedMay 18, 2025
edited
Loading

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

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 addingcdce8p/setup-python@* as trusted workflow. (Already did so, otherwise the workflow wouldn't have run here probably.)

@Pierre-Sassoulas
Copy link
Member

No you're right if your account is compromised it's already game over

@Pierre-SassoulasPierre-Sassoulas merged commit58813cd intopylint-dev:mainMay 18, 2025
41 checks passed
@ghost
Copy link

The backport tomaintenance/3.3.x failed:

The process '/usr/bin/git' failed with exit code 1

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 thebase branch ismaintenance/3.3.x and thecompare/head branch isbackport-10392-to-maintenance/3.3.x.

@cdce8p
Copy link
MemberAuthor

Let's not backport this one. The CI for the maintenance branch is fine without it.

Pierre-Sassoulas reacted with thumbs up emoji

@cdce8pcdce8p deleted the fix-pypy-cache branchMay 18, 2025 20:42
@cdce8pcdce8p modified the milestones:3.3.8,4.0.0Aug 15, 2025
Sign up for freeto join this conversation on GitHub. Already have an account?Sign in to comment

Reviewers

@Pierre-SassoulasPierre-SassoulasPierre-Sassoulas approved these changes

Assignees

No one assigned

Labels

MaintenanceDiscussion or action around maintaining pylint or the dev workflowSkip news 🔇This change does not require a changelog entry

Projects

None yet

Milestone

4.0.0

Development

Successfully merging this pull request may close these issues.

2 participants

@cdce8p@Pierre-Sassoulas

[8]ページ先頭

©2009-2025 Movatter.jp