GitHub windows-latest runner image 20250602.1.0 seems to break cached Poetry

Open
#7 4 comments 0 reactions 1 assignee View on GitHub

@bkeryan is already working on this.

Since Jun 6, 2025.

  • #8 by @bkeryan — merged

Assessment

This issue has not been assessed yet.

Description

bug

Bug Report

Today, PR workflows started failing with errors running poetry and/or pytest.

Repro or Code Sample

https://github.com/ni/nitypes-python/actions/runs/15496692627/job/43640756105 retry number 8

Run ni/python-actions/setup-poetry@2c946e7237558ed6d59565787f1edb2150df50ba
Run if [ ! -d "$pythonLocation" ]; then
Run Add-Content $env:GITHUB_ENV "POETRY_BIN_DIR=$HOME\.local\poetry\bin"
Run echo "poetry-bin-dir=$POETRY_BIN_DIR" >> "$GITHUB_OUTPUT"
Run actions/cache@5a3ec84eff668545956fd18022155c47e93e2684
Cache hit for: poetry1.8.2-Windows-py3.11.9
Received 19099528 of 19099528 ([10](https://github.com/ni/nitypes-python/actions/runs/15496692627/job/43640756115#step:4:11)0.0%), 61.3 MBs/sec
Cache Size: ~18 MB (19099528 B)
"C:\Program Files\Git\usr\bin\tar.exe" -xf D:/a/_temp/64cd2eea-d3c3-4546-90d7-d7d3076f11ba/cache.tzst -P -C D:/a/nitypes-python/nitypes-python --force-local --use-compress-program "zstd -d"
Cache restored successfully
Cache restored from key: poetry1.8.2-Windows-py3.11.9
Run poetry --version
D:\a\_temp\5bee54b4-5547-4a7f-8255-24[68](https://github.com/ni/nitypes-python/actions/runs/15496692627/job/43640756115#step:4:73)5d6c2734.sh: line 1: poetry: command not found
Error: Process completed with exit code 127.

Expected Behavior

Poetry works.

Current Behavior

The passing jobs have windows-2022 runner image 20250511.1.0.

The failing jobs have windows-2022 runner image 20250602.1.0 and fail with poetry: command not found

Possible Solution

Add runner image name/version to cache key.

Add an input to disable caching.

Context

This is breaking PR workflows.

Your Environment

  • ni/python-actions version: v0.2.0
  • Python version: default

AB#3154927

Dominant language
Python
Stars
2
Forks
0
Avg merge
2d 5h
Merged PRs (30d)
1

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from ni/python-actions

All issues in ni/python-actions

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.