ci: do not force python 3.11.9 over the image interpreter - #3
Merged
Conversation
rocker/ml ships a complete /opt/venv on Python 3.14. Requesting 3.11.9 makes setup-python install a second interpreter that shadows it, discarding every preinstalled package and forcing pip to rebuild the stack -- which is how the pinned duckdb ended up compiling from source and hitting the memory limit.
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
1 participant
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.
Drops
python-version: '3.11.9'from thesetup-pythonstep.On the
arc-runner-espm157runner this input is actively harmful. The job runs inrocker/ml, which ships a complete/opt/venv— Python 3.14.4 with pandas, duckdb 1.5.5, ibis 12.0.0, plotnine, pyarrow and the rest already installed. Asking for 3.11.9 makessetup-pythondownload and prepend a separate interpreter, which shadows/opt/venvand throws away every preinstalled package. Everything inrequirements.txtthen has to be rebuilt from scratch against an interpreter the image was never built for.That is also how the
exit 137failures happened: against 3.14 the pinnedduckdb==1.3.2had no matching wheel (cp313is its newest tag), so pip compiled DuckDB from source until the job pod hit its memory limit and was SIGKILLed.With the input removed,
setup-pythonuses the interpreter already onPATH— the image's — andpip install -r requirements.txtresolves to "already satisfied" for the scientific stack, installing only the few small pure-Python test deps.No effect on the
ubuntu-latestfallback path for public forks, which picks up the hosted runner's default Python the same way.