Skip to content
PR

Allow adding install-args to the poetry install command in analyze-project #168

Sign in to view logs

Allow adding install-args to the poetry install command in analyze-project

Allow adding install-args to the poetry install command in analyze-project #168

Triggered via pull request September 29, 2025 21:29
@dixonjoeldixonjoel
synchronize #40
users/jdixon/add-dependency-groups
Status Success
Total duration 8m 49s
Artifacts –

PR.yml

on: pull_request
Matrix: Run CI / Test actions / Test setup-poetry
Matrix: Run CI / Test actions / Test analyze-project
Matrix: Run CI / Test actions / Test analyze-project (repo root)
Matrix: Run CI / Test actions / Test setup-python
Run CI  /  ...  /  Test check-project-version
22s
Run CI / Test actions / Test check-project-version
Run CI  /  ...  /  Test update-project-version
27s
Run CI / Test actions / Test update-project-version
Matrix: Run CI / Test actions / Test setup-poetry (cache hit)
Matrix: Run CI / Test actions / Test setup-poetry (no cache)
Matrix: Run CI / Test actions / Test analyze-project (cache hit)
Run CI  /  ...  /  Test Results
2s
Run CI / Test actions / Test Results
Fit to window
Zoom out
Zoom in

Annotations

128 errors and 51 notices
Run CI / Test actions / Test check-project-version
Process completed with exit code 1.
Project Version Error
The project version in pyproject.toml does not match the expected version. If this workflow was triggered by a GitHub release, verify that the release was tagged with the correct version. If they don't match, you should either update pyproject.toml or delete and re-create the release with the correct tag. Project version: 1.0.0 Expected version: 1.0.1
Run CI / Test actions / Test analyze-project (ubuntu-latest, 3.11)
Process completed with exit code 1.
Run CI / Test actions / Test analyze-project (ubuntu-latest, 3.11)
Process completed with exit code 255.
Run CI / Test actions / Test analyze-project (ubuntu-latest, 3.11)
Process completed with exit code 255.
Run CI / Test actions / Test analyze-project (ubuntu-latest, 3.13)
Process completed with exit code 1.
Run CI / Test actions / Test analyze-project (ubuntu-latest, 3.13)
Process completed with exit code 255.
Run CI / Test actions / Test analyze-project (ubuntu-latest, 3.13)
Process completed with exit code 255.
Run CI / Test actions / Test analyze-project (ubuntu-latest, 3.12)
Process completed with exit code 1.
Run CI / Test actions / Test analyze-project (ubuntu-latest, 3.12)
Process completed with exit code 255.
Run CI / Test actions / Test analyze-project (ubuntu-latest, 3.12)
Process completed with exit code 255.
Run CI / Test actions / Test analyze-project (ubuntu-latest, 3.9)
Process completed with exit code 1.
Run CI / Test actions / Test analyze-project (ubuntu-latest, 3.9)
Process completed with exit code 255.
Run CI / Test actions / Test analyze-project (ubuntu-latest, 3.9)
Process completed with exit code 255.
Run CI / Test actions / Test analyze-project (macos-latest, 3.11)
Process completed with exit code 1.
Run CI / Test actions / Test analyze-project (macos-latest, 3.11)
Process completed with exit code 255.
Run CI / Test actions / Test analyze-project (macos-latest, 3.11)
Process completed with exit code 255.
Run CI / Test actions / Test analyze-project (macos-latest, 3.12)
Process completed with exit code 1.
Run CI / Test actions / Test analyze-project (macos-latest, 3.12)
Process completed with exit code 255.
Run CI / Test actions / Test analyze-project (macos-latest, 3.12)
Process completed with exit code 255.
Run CI / Test actions / Test analyze-project (macos-latest, 3.13)
Process completed with exit code 1.
Run CI / Test actions / Test analyze-project (macos-latest, 3.13)
Process completed with exit code 255.
Run CI / Test actions / Test analyze-project (macos-latest, 3.13)
Process completed with exit code 255.
Run CI / Test actions / Test analyze-project (ubuntu-latest, 3.10)
Process completed with exit code 1.
Run CI / Test actions / Test analyze-project (ubuntu-latest, 3.10)
Process completed with exit code 255.
Run CI / Test actions / Test analyze-project (ubuntu-latest, 3.10)
Process completed with exit code 255.
Run CI / Test actions / Test analyze-project (macos-latest, 3.10)
Process completed with exit code 1.
Run CI / Test actions / Test analyze-project (macos-latest, 3.10)
Process completed with exit code 255.
Run CI / Test actions / Test analyze-project (macos-latest, 3.10)
Process completed with exit code 255.
Run CI / Test actions / Test analyze-project (macos-latest, 3.9)
Process completed with exit code 1.
Run CI / Test actions / Test analyze-project (macos-latest, 3.9)
Process completed with exit code 255.
Run CI / Test actions / Test analyze-project (macos-latest, 3.9)
Process completed with exit code 255.
Run CI / Test actions / Test analyze-project (ubuntu-latest, pypy3.11)
Process completed with exit code 1.
Run CI / Test actions / Test analyze-project (ubuntu-latest, pypy3.11)
Process completed with exit code 255.
Run CI / Test actions / Test analyze-project (ubuntu-latest, pypy3.11)
Process completed with exit code 255.
Run CI / Test actions / Test analyze-project (macos-latest, pypy3.10)
Process completed with exit code 1.
Run CI / Test actions / Test analyze-project (macos-latest, pypy3.10)
Process completed with exit code 255.
Run CI / Test actions / Test analyze-project (macos-latest, pypy3.10)
Process completed with exit code 255.
Run CI / Test actions / Test analyze-project (macos-latest, pypy3.11)
Process completed with exit code 1.
Run CI / Test actions / Test analyze-project (macos-latest, pypy3.11)
Process completed with exit code 255.
Run CI / Test actions / Test analyze-project (macos-latest, pypy3.11)
Process completed with exit code 255.
Run CI / Test actions / Test analyze-project (ubuntu-latest, pypy3.10)
Process completed with exit code 1.
Run CI / Test actions / Test analyze-project (ubuntu-latest, pypy3.10)
Process completed with exit code 255.
Run CI / Test actions / Test analyze-project (ubuntu-latest, pypy3.10)
Process completed with exit code 255.
Run CI / Test actions / Test analyze-project (windows-latest, 3.9)
Process completed with exit code 1.
Run CI / Test actions / Test analyze-project (windows-latest, 3.9)
Process completed with exit code 127.
Run CI / Test actions / Test analyze-project (windows-latest, 3.9)
Process completed with exit code 127.
Run CI / Test actions / Test analyze-project (windows-latest, 3.12)
Process completed with exit code 1.
Run CI / Test actions / Test analyze-project (windows-latest, 3.12)
Process completed with exit code 127.
Run CI / Test actions / Test analyze-project (windows-latest, 3.12)
Process completed with exit code 127.
Run CI / Test actions / Test analyze-project (windows-latest, 3.10)
Process completed with exit code 1.
Run CI / Test actions / Test analyze-project (windows-latest, 3.10)
Process completed with exit code 127.
Run CI / Test actions / Test analyze-project (windows-latest, 3.10)
Process completed with exit code 127.
Run CI / Test actions / Test analyze-project (windows-latest, 3.11)
Process completed with exit code 1.
Run CI / Test actions / Test analyze-project (windows-latest, 3.11)
Process completed with exit code 127.
Run CI / Test actions / Test analyze-project (windows-latest, 3.11)
Process completed with exit code 127.
Run CI / Test actions / Test analyze-project (windows-latest, 3.13)
Process completed with exit code 1.
Run CI / Test actions / Test analyze-project (windows-latest, 3.13)
Process completed with exit code 127.
Run CI / Test actions / Test analyze-project (windows-latest, 3.13)
Process completed with exit code 127.
Run CI / Test actions / Test analyze-project (windows-latest, pypy3.10)
Process completed with exit code 1.
Run CI / Test actions / Test analyze-project (windows-latest, pypy3.10)
Process completed with exit code 127.
Run CI / Test actions / Test analyze-project (windows-latest, pypy3.10)
Process completed with exit code 127.
Run CI / Test actions / Test analyze-project (windows-latest, pypy3.11)
Process completed with exit code 1.
Run CI / Test actions / Test analyze-project (windows-latest, pypy3.11)
Process completed with exit code 127.
Run CI / Test actions / Test analyze-project (windows-latest, pypy3.11)
Process completed with exit code 127.
Run CI / Test actions / Test analyze-project (cache hit) (ubuntu-latest, 3.9)
Process completed with exit code 1.
Run CI / Test actions / Test analyze-project (cache hit) (ubuntu-latest, 3.9)
Process completed with exit code 255.
Run CI / Test actions / Test analyze-project (cache hit) (ubuntu-latest, 3.9)
Process completed with exit code 255.
Run CI / Test actions / Test analyze-project (cache hit) (ubuntu-latest, 3.12)
Process completed with exit code 1.
Run CI / Test actions / Test analyze-project (cache hit) (ubuntu-latest, 3.12)
Process completed with exit code 255.
Run CI / Test actions / Test analyze-project (cache hit) (ubuntu-latest, 3.12)
Process completed with exit code 255.
Run CI / Test actions / Test analyze-project (cache hit) (ubuntu-latest, 3.13)
Process completed with exit code 1.
Run CI / Test actions / Test analyze-project (cache hit) (ubuntu-latest, 3.13)
Process completed with exit code 255.
Run CI / Test actions / Test analyze-project (cache hit) (ubuntu-latest, 3.13)
Process completed with exit code 255.
Run CI / Test actions / Test analyze-project (cache hit) (ubuntu-latest, 3.10)
Process completed with exit code 1.
Run CI / Test actions / Test analyze-project (cache hit) (ubuntu-latest, 3.10)
Process completed with exit code 255.
Run CI / Test actions / Test analyze-project (cache hit) (ubuntu-latest, 3.10)
Process completed with exit code 255.
Run CI / Test actions / Test analyze-project (cache hit) (ubuntu-latest, 3.11)
Process completed with exit code 1.
Run CI / Test actions / Test analyze-project (cache hit) (ubuntu-latest, 3.11)
Process completed with exit code 255.
Run CI / Test actions / Test analyze-project (cache hit) (ubuntu-latest, 3.11)
Process completed with exit code 255.
Run CI / Test actions / Test analyze-project (cache hit) (macos-latest, 3.11)
Process completed with exit code 1.
Run CI / Test actions / Test analyze-project (cache hit) (macos-latest, 3.11)
Process completed with exit code 255.
Run CI / Test actions / Test analyze-project (cache hit) (macos-latest, 3.11)
Process completed with exit code 255.
Run CI / Test actions / Test analyze-project (cache hit) (macos-latest, 3.13)
Process completed with exit code 1.
Run CI / Test actions / Test analyze-project (cache hit) (macos-latest, 3.13)
Process completed with exit code 255.
Run CI / Test actions / Test analyze-project (cache hit) (macos-latest, 3.13)
Process completed with exit code 255.
Run CI / Test actions / Test analyze-project (cache hit) (macos-latest, 3.12)
Process completed with exit code 1.
Run CI / Test actions / Test analyze-project (cache hit) (macos-latest, 3.12)
Process completed with exit code 255.
Run CI / Test actions / Test analyze-project (cache hit) (macos-latest, 3.12)
Process completed with exit code 255.
Run CI / Test actions / Test analyze-project (cache hit) (macos-latest, 3.10)
Process completed with exit code 1.
Run CI / Test actions / Test analyze-project (cache hit) (macos-latest, 3.10)
Process completed with exit code 255.
Run CI / Test actions / Test analyze-project (cache hit) (macos-latest, 3.10)
Process completed with exit code 255.
Run CI / Test actions / Test analyze-project (cache hit) (ubuntu-latest, pypy3.11)
Process completed with exit code 1.
Run CI / Test actions / Test analyze-project (cache hit) (ubuntu-latest, pypy3.11)
Process completed with exit code 255.
Run CI / Test actions / Test analyze-project (cache hit) (ubuntu-latest, pypy3.11)
Process completed with exit code 255.
Run CI / Test actions / Test analyze-project (cache hit) (ubuntu-latest, pypy3.10)
Process completed with exit code 1.
Run CI / Test actions / Test analyze-project (cache hit) (ubuntu-latest, pypy3.10)
Process completed with exit code 255.
Run CI / Test actions / Test analyze-project (cache hit) (ubuntu-latest, pypy3.10)
Process completed with exit code 255.
Run CI / Test actions / Test analyze-project (cache hit) (macos-latest, 3.9)
Process completed with exit code 1.
Run CI / Test actions / Test analyze-project (cache hit) (macos-latest, 3.9)
Process completed with exit code 255.
Run CI / Test actions / Test analyze-project (cache hit) (macos-latest, 3.9)
Process completed with exit code 255.
Run CI / Test actions / Test analyze-project (cache hit) (macos-latest, pypy3.11)
Process completed with exit code 1.
Run CI / Test actions / Test analyze-project (cache hit) (macos-latest, pypy3.11)
Process completed with exit code 255.
Run CI / Test actions / Test analyze-project (cache hit) (macos-latest, pypy3.11)
Process completed with exit code 255.
Run CI / Test actions / Test analyze-project (cache hit) (windows-latest, 3.12)
Process completed with exit code 1.
Run CI / Test actions / Test analyze-project (cache hit) (windows-latest, 3.12)
Process completed with exit code 127.
Run CI / Test actions / Test analyze-project (cache hit) (windows-latest, 3.12)
Process completed with exit code 127.
Run CI / Test actions / Test analyze-project (cache hit) (macos-latest, pypy3.10)
Process completed with exit code 1.
Run CI / Test actions / Test analyze-project (cache hit) (macos-latest, pypy3.10)
Process completed with exit code 255.
Run CI / Test actions / Test analyze-project (cache hit) (macos-latest, pypy3.10)
Process completed with exit code 255.
Run CI / Test actions / Test analyze-project (cache hit) (windows-latest, 3.9)
Process completed with exit code 1.
Run CI / Test actions / Test analyze-project (cache hit) (windows-latest, 3.9)
Process completed with exit code 127.
Run CI / Test actions / Test analyze-project (cache hit) (windows-latest, 3.9)
Process completed with exit code 127.
Run CI / Test actions / Test analyze-project (cache hit) (windows-latest, 3.10)
Process completed with exit code 1.
Run CI / Test actions / Test analyze-project (cache hit) (windows-latest, 3.10)
Process completed with exit code 127.
Run CI / Test actions / Test analyze-project (cache hit) (windows-latest, 3.10)
Process completed with exit code 127.
Run CI / Test actions / Test analyze-project (cache hit) (windows-latest, 3.13)
Process completed with exit code 1.
Run CI / Test actions / Test analyze-project (cache hit) (windows-latest, 3.13)
Process completed with exit code 127.
Run CI / Test actions / Test analyze-project (cache hit) (windows-latest, 3.13)
Process completed with exit code 127.
Run CI / Test actions / Test analyze-project (cache hit) (windows-latest, 3.11)
Process completed with exit code 1.
Run CI / Test actions / Test analyze-project (cache hit) (windows-latest, 3.11)
Process completed with exit code 127.
Run CI / Test actions / Test analyze-project (cache hit) (windows-latest, 3.11)
Process completed with exit code 127.
Run CI / Test actions / Test analyze-project (cache hit) (windows-latest, pypy3.10)
Process completed with exit code 1.
Run CI / Test actions / Test analyze-project (cache hit) (windows-latest, pypy3.10)
Process completed with exit code 127.
Run CI / Test actions / Test analyze-project (cache hit) (windows-latest, pypy3.10)
Process completed with exit code 127.
Run CI / Test actions / Test analyze-project (cache hit) (windows-latest, pypy3.11)
Process completed with exit code 1.
Run CI / Test actions / Test analyze-project (cache hit) (windows-latest, pypy3.11)
Process completed with exit code 127.
Run CI / Test actions / Test analyze-project (cache hit) (windows-latest, pypy3.11)
Process completed with exit code 127.
Run CI / Test actions / Test setup-python (windows-latest, 3.11)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
Run CI / Test actions / Test setup-python (windows-latest, 3.12)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
Run CI / Test actions / Test setup-python (windows-latest, 3.10)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
Run CI / Test actions / Test setup-python (windows-latest, 3.9)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
Run CI / Test actions / Test setup-python (windows-latest, pypy3.10)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
Notice
The next step is expected to fail.
Run CI / Test actions / Test setup-poetry (windows-latest, 3.9)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
Run CI / Test actions / Test setup-poetry (windows-latest, 3.13)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
Run CI / Test actions / Test setup-poetry (windows-latest, 3.10)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
Run CI / Test actions / Test setup-poetry (windows-latest, 3.12)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
Run CI / Test actions / Test setup-python (windows-latest, pypy3.11)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
Run CI / Test actions / Test setup-python (windows-latest, 3.13)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
Run CI / Test actions / Test setup-poetry (windows-latest, pypy3.10)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
Run CI / Test actions / Test setup-poetry (windows-latest, pypy3.11)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
Run CI / Test actions / Test analyze-project (repo root) (windows-latest, 3.12)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
Run CI / Test actions / Test analyze-project (repo root) (windows-latest, 3.9)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
Run CI / Test actions / Test analyze-project (repo root) (windows-latest, 3.10)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
Run CI / Test actions / Test setup-poetry (windows-latest, 3.11)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
Run CI / Test actions / Test setup-python (windows-latest, 3.13t)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
Run CI / Test actions / Test analyze-project (repo root) (windows-latest, 3.11)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
Run CI / Test actions / Test analyze-project (repo root) (windows-latest, 3.13)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
Run CI / Test actions / Test setup-poetry (cache hit) (windows-latest, 3.10)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
Run CI / Test actions / Test analyze-project (repo root) (windows-latest, pypy3.11)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
Run CI / Test actions / Test analyze-project (windows-latest, 3.9)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
Run CI / Test actions / Test setup-poetry (no cache) (windows-latest, 3.12)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
Run CI / Test actions / Test setup-poetry (cache hit) (windows-latest, 3.13)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
Run CI / Test actions / Test setup-poetry (cache hit) (windows-latest, pypy3.10)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
Run CI / Test actions / Test setup-poetry (no cache) (windows-latest, 3.13)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
Run CI / Test actions / Test setup-poetry (cache hit) (windows-latest, 3.12)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
Run CI / Test actions / Test setup-poetry (no cache) (windows-latest, 3.9)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
Run CI / Test actions / Test setup-poetry (cache hit) (windows-latest, 3.9)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
Run CI / Test actions / Test setup-poetry (cache hit) (windows-latest, 3.11)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
Run CI / Test actions / Test analyze-project (windows-latest, 3.12)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
Run CI / Test actions / Test setup-poetry (no cache) (windows-latest, 3.11)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
Run CI / Test actions / Test setup-poetry (cache hit) (windows-latest, pypy3.11)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
Run CI / Test actions / Test analyze-project (windows-latest, 3.10)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
Run CI / Test actions / Test setup-poetry (no cache) (windows-latest, 3.10)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
Run CI / Test actions / Test analyze-project (windows-latest, 3.11)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
Run CI / Test actions / Test setup-poetry (no cache) (windows-latest, pypy3.10)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
Run CI / Test actions / Test analyze-project (windows-latest, 3.13)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
Run CI / Test actions / Test analyze-project (repo root) (windows-latest, pypy3.10)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
Run CI / Test actions / Test analyze-project (windows-latest, pypy3.10)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
Run CI / Test actions / Test setup-poetry (no cache) (windows-latest, pypy3.11)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
Run CI / Test actions / Test analyze-project (windows-latest, pypy3.11)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
Run CI / Test actions / Test analyze-project (cache hit) (windows-latest, 3.12)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
Run CI / Test actions / Test analyze-project (cache hit) (windows-latest, 3.9)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
Run CI / Test actions / Test analyze-project (cache hit) (windows-latest, 3.10)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
Run CI / Test actions / Test analyze-project (cache hit) (windows-latest, 3.13)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
Run CI / Test actions / Test analyze-project (cache hit) (windows-latest, 3.11)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
Run CI / Test actions / Test analyze-project (cache hit) (windows-latest, pypy3.10)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
Run CI / Test actions / Test analyze-project (cache hit) (windows-latest, pypy3.11)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677