Skip to content
PR

PR #138

Sign in to view logs

PR

PR #138

Manually triggered September 26, 2025 20:31
@bkeryanbkeryan
⁠ 56d7350
users/bkeryan/fix-setup-poetry-dir
Status Cancelled
Total duration 4m 26s
Artifacts –

PR.yml

on: workflow_dispatch
Matrix: Run CI / Test actions / Test setup-poetry
Matrix: Run CI / Test actions / Test analyze-project
Matrix: Run CI / Test actions / Test analyze-project in root of repo
Matrix: Run CI / Test actions / Test setup-python
Run CI  /  ...  /  Test check-project-version
20s
Run CI / Test actions / Test check-project-version
Run CI  /  ...  /  Test update-project-version
28s
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)
Run CI  /  ...  /  Test Results
0s
Run CI / Test actions / Test Results
Fit to window
Zoom out
Zoom in

Annotations

51 errors, 1 warning, and 44 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 in root of repo (windows-latest, 3.10)
Process completed with exit code 1.
Run CI / Test actions / Test analyze-project in root of repo (windows-latest, 3.11)
The strategy configuration was canceled because "run_ci.test_actions.test_analyze_project_in_root.windows-latest_3_10" failed
Run CI / Test actions / Test analyze-project in root of repo (windows-latest, pypy3.10)
Process completed with exit code 1.
Run CI / Test actions / Test analyze-project in root of repo (windows-latest, pypy3.10)
The strategy configuration was canceled because "run_ci.test_actions.test_analyze_project_in_root.windows-latest_3_10" failed
Run CI / Test actions / Test analyze-project in root of repo (windows-latest, 3.12)
Process completed with exit code 1.
Run CI / Test actions / Test analyze-project in root of repo (windows-latest, 3.12)
The strategy configuration was canceled because "run_ci.test_actions.test_analyze_project_in_root.windows-latest_3_10" failed
Run CI / Test actions / Test analyze-project in root of repo (windows-latest, 3.9)
Process completed with exit code 1.
Run CI / Test actions / Test analyze-project in root of repo (windows-latest, 3.9)
The strategy configuration was canceled because "run_ci.test_actions.test_analyze_project_in_root.windows-latest_3_10" failed
Run CI / Test actions / Test analyze-project in root of repo (macos-latest, 3.10)
The operation was canceled.
Run CI / Test actions / Test analyze-project in root of repo (macos-latest, 3.10)
The strategy configuration was canceled because "run_ci.test_actions.test_analyze_project_in_root.windows-latest_3_10" failed
Run CI / Test actions / Test analyze-project in root of repo (macos-latest, pypy3.10)
The operation was canceled.
Run CI / Test actions / Test analyze-project in root of repo (macos-latest, pypy3.10)
The strategy configuration was canceled because "run_ci.test_actions.test_analyze_project_in_root.windows-latest_3_10" failed
Run CI / Test actions / Test analyze-project in root of repo (macos-latest, 3.9)
The operation was canceled.
Run CI / Test actions / Test analyze-project in root of repo (macos-latest, 3.9)
The strategy configuration was canceled because "run_ci.test_actions.test_analyze_project_in_root.windows-latest_3_10" failed
Run CI / Test actions / Test analyze-project in root of repo (ubuntu-latest, pypy3.10)
The operation was canceled.
Run CI / Test actions / Test analyze-project in root of repo (ubuntu-latest, pypy3.10)
The strategy configuration was canceled because "run_ci.test_actions.test_analyze_project_in_root.windows-latest_3_10" failed
Run CI / Test actions / Test analyze-project in root of repo (macos-latest, pypy3.11)
The operation was canceled.
Run CI / Test actions / Test analyze-project in root of repo (macos-latest, pypy3.11)
The strategy configuration was canceled because "run_ci.test_actions.test_analyze_project_in_root.windows-latest_3_10" failed
Run CI / Test actions / Test analyze-project in root of repo (windows-latest, 3.13)
The operation was canceled.
Run CI / Test actions / Test analyze-project in root of repo (windows-latest, 3.13)
The strategy configuration was canceled because "run_ci.test_actions.test_analyze_project_in_root.windows-latest_3_10" failed
Run CI / Test actions / Test analyze-project in root of repo (windows-latest, pypy3.11)
not a git repository (or any of the parent directories): .git
Run CI / Test actions / Test analyze-project in root of repo (windows-latest, pypy3.11)
--local can only be used inside a git repository
Run CI / Test actions / Test analyze-project in root of repo (windows-latest, pypy3.11)
The operation was canceled.
Run CI / Test actions / Test analyze-project in root of repo (windows-latest, pypy3.11)
The strategy configuration was canceled because "run_ci.test_actions.test_analyze_project_in_root.windows-latest_3_10" failed
Run CI / Test actions / Test analyze-project in root of repo (ubuntu-latest, pypy3.11)
The operation was canceled.
Run CI / Test actions / Test analyze-project in root of repo (ubuntu-latest, pypy3.11)
The strategy configuration was canceled because "run_ci.test_actions.test_analyze_project_in_root.windows-latest_3_10" failed
Run CI / Test actions / Test analyze-project in root of repo (ubuntu-latest, 3.11)
The operation was canceled.
Run CI / Test actions / Test analyze-project in root of repo (ubuntu-latest, 3.11)
The strategy configuration was canceled because "run_ci.test_actions.test_analyze_project_in_root.windows-latest_3_10" failed
Run CI / Test actions / Test analyze-project in root of repo (ubuntu-latest, 3.9)
The operation was canceled.
Run CI / Test actions / Test analyze-project in root of repo (ubuntu-latest, 3.9)
The strategy configuration was canceled because "run_ci.test_actions.test_analyze_project_in_root.windows-latest_3_10" failed
Run CI / Test actions / Test analyze-project in root of repo (ubuntu-latest, 3.13)
The operation was canceled.
Run CI / Test actions / Test analyze-project in root of repo (ubuntu-latest, 3.13)
The strategy configuration was canceled because "run_ci.test_actions.test_analyze_project_in_root.windows-latest_3_10" failed
Run CI / Test actions / Test analyze-project in root of repo (ubuntu-latest, 3.10)
The operation was canceled.
Run CI / Test actions / Test analyze-project in root of repo (ubuntu-latest, 3.10)
The strategy configuration was canceled because "run_ci.test_actions.test_analyze_project_in_root.windows-latest_3_10" failed
Run CI / Test actions / Test analyze-project in root of repo (ubuntu-latest, 3.12)
The operation was canceled.
Run CI / Test actions / Test analyze-project in root of repo (ubuntu-latest, 3.12)
The strategy configuration was canceled because "run_ci.test_actions.test_analyze_project_in_root.windows-latest_3_10" failed
Run CI / Test actions / Test analyze-project in root of repo (macos-latest, 3.11)
The operation was canceled.
Run CI / Test actions / Test analyze-project in root of repo (macos-latest, 3.11)
The strategy configuration was canceled because "run_ci.test_actions.test_analyze_project_in_root.windows-latest_3_10" failed
Run CI / Test actions / Test analyze-project in root of repo (macos-latest, 3.12)
The operation was canceled.
Run CI / Test actions / Test analyze-project in root of repo (macos-latest, 3.12)
The strategy configuration was canceled because "run_ci.test_actions.test_analyze_project_in_root.windows-latest_3_10" failed
Run CI / Test actions / Test analyze-project in root of repo (macos-latest, 3.13)
The operation was canceled.
Run CI / Test actions / Test analyze-project in root of repo (macos-latest, 3.13)
The strategy configuration was canceled because "run_ci.test_actions.test_analyze_project_in_root.windows-latest_3_10" failed
Run CI / Test actions / Test setup-poetry (no cache) (ubuntu-latest, pypy3.10)
The operation was canceled.
Run CI / Test actions / Test setup-poetry (no cache) (ubuntu-latest, pypy3.10)
The run was canceled by @bkeryan.
Run CI / Test actions / Test setup-poetry (no cache) (ubuntu-latest, pypy3.11)
The operation was canceled.
Run CI / Test actions / Test setup-poetry (no cache) (ubuntu-latest, pypy3.11)
The run was canceled by @bkeryan.
PR
The run was canceled by @bkeryan.
PR
The run was canceled by @bkeryan.
PR
The run was canceled by @bkeryan.
Run CI / Test actions / Test analyze-project in root of repo (windows-latest, pypy3.11)
The process 'C:\Program Files\Git\bin\git.exe' failed with exit code 128
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-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.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, 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-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
Notice
The next step is expected to fail.
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-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-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 analyze-project in root of repo (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 in root of repo (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 in root of repo (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, 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 in root of repo (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 in root of repo (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.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 in root of repo (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 analyze-project in root of repo (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-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, 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 (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.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 (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 (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.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 (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 (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 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 (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 (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 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 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 (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, 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.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 (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 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 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 (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 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 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