Repository navigation
Fix Python 2.7 CI image for v4.3.1-dev - #495
Merged
Merged
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.
The Python 2.7 pytest job fails before tests start because
python:2.7.11-wheezyhas legacy image metadata that modern Docker/containerd cannot unpack. Replace it with the available officialpython:2.7.18-busterimage and useactions/checkout@v4, which its newer glibc supports.This retains Python 2.7 coverage but moves the patch-level target from 2.7.11 to 2.7.18.
Validation: pulled and ran
python:2.7.18-busterfor Linux amd64 with the existing virtualenv/pip/dependency setup. The existing pytest suite passed: 1,452 passed, 15 skipped. Workflow YAML parsing andgit diff --checkalso passed. Local container validation used Podman; the GitHub Actions run will verify Docker and checkout on the hosted runner.