Repository navigation
ci: pin the Python test job to ubuntu-24.04 - #678
Open
yadavchiragg wants to merge 1 commit into
Open
yadavchiragg wants to merge 1 commit into
yadavchiragg wants to merge 1 commit into
Conversation
This file contains hidden or 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
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.
Problem: the
testjob runs onubuntu-latestwith a Python 3.9 to 3.12 matrix. GitHub is moving theubuntu-latestlabel to Ubuntu 26.04, andactions/setup-pythonhas no Python 3.9 build for it, so the 3.9 job fails with "The version '3.9' with architecture 'x64' was not found for Ubuntu 26.04". Because the matrix uses the defaultfail-fast, the 3.10, 3.11 and 3.12 jobs are then cancelled, so the whole Python test job goes red regardless of the code.Change: pin only the
testjob toubuntu-24.04. The other jobs are unchanged (they pass on the new image).Testing: reproduced the failure on my fork and confirmed that all four
test (3.9)totest (3.12)jobs pass with the pin.If you would rather drop Python 3.9 (it is past end of life) instead of pinning, I'm happy to change this PR to do that.