Test actions #1
bkeryantest_actions.yml
on: workflow_dispatch
Matrix: Test setup-poetry
Matrix: Test analyze-project
Matrix: Test analyze-project in root of repo
Matrix: Test setup-python
Test check-project-version
21s
Test update-project-version
20s
Matrix: Test setup-poetry (cache hit)
Matrix: Test setup-poetry (no cache)
Test Results
0s
Annotations
57 errors and 44 notices
|
Test analyze-project in root of repo (ubuntu-latest, 3.13)
Process completed with exit code 1.
|
|
Test analyze-project in root of repo (macos-latest, 3.13)
Process completed with exit code 1.
|
|
Test analyze-project in root of repo (ubuntu-latest, 3.9)
Process completed with exit code 1.
|
|
Test analyze-project in root of repo (ubuntu-latest, 3.9)
The strategy configuration was canceled because "test_analyze_project_in_root.ubuntu-latest_3_13" failed
|
|
Test analyze-project in root of repo (ubuntu-latest, 3.12)
Process completed with exit code 1.
|
|
Test analyze-project in root of repo (ubuntu-latest, 3.12)
The strategy configuration was canceled because "test_analyze_project_in_root.ubuntu-latest_3_13" failed
|
|
Test analyze-project in root of repo (macos-latest, 3.11)
Process completed with exit code 1.
|
|
Test analyze-project in root of repo (macos-latest, 3.11)
The strategy configuration was canceled because "test_analyze_project_in_root.ubuntu-latest_3_13" failed
|
|
Test analyze-project in root of repo (ubuntu-latest, pypy3.11)
The operation was canceled.
|
|
Test analyze-project in root of repo (ubuntu-latest, pypy3.11)
The strategy configuration was canceled because "test_analyze_project_in_root.ubuntu-latest_3_13" failed
|
|
Test analyze-project in root of repo (windows-latest, 3.9)
The operation was canceled.
|
|
Test analyze-project in root of repo (windows-latest, 3.9)
The strategy configuration was canceled because "test_analyze_project_in_root.ubuntu-latest_3_13" failed
|
|
Test analyze-project in root of repo (windows-latest, 3.12)
A task was canceled.
|
|
Test analyze-project in root of repo (windows-latest, 3.12)
The strategy configuration was canceled because "test_analyze_project_in_root.ubuntu-latest_3_13" failed
|
|
Test analyze-project in root of repo (ubuntu-latest, 3.10)
Process completed with exit code 1.
|
|
Test analyze-project in root of repo (ubuntu-latest, 3.10)
The strategy configuration was canceled because "test_analyze_project_in_root.ubuntu-latest_3_13" failed
|
|
Test analyze-project in root of repo (macos-latest, 3.10)
The operation was canceled.
|
|
Test analyze-project in root of repo (macos-latest, 3.10)
The strategy configuration was canceled because "test_analyze_project_in_root.ubuntu-latest_3_13" failed
|
|
Test analyze-project in root of repo (windows-latest, 3.11)
The operation was canceled.
|
|
Test analyze-project in root of repo (windows-latest, 3.11)
The strategy configuration was canceled because "test_analyze_project_in_root.ubuntu-latest_3_13" failed
|
|
Test analyze-project in root of repo (macos-latest, 3.9)
The operation was canceled.
|
|
Test analyze-project in root of repo (macos-latest, 3.9)
The strategy configuration was canceled because "test_analyze_project_in_root.ubuntu-latest_3_13" failed
|
|
Test analyze-project in root of repo (macos-latest, 3.12)
The operation was canceled.
|
|
Test analyze-project in root of repo (macos-latest, 3.12)
The strategy configuration was canceled because "test_analyze_project_in_root.ubuntu-latest_3_13" failed
|
|
Test analyze-project in root of repo (ubuntu-latest, 3.11)
The operation was canceled.
|
|
Test analyze-project in root of repo (ubuntu-latest, 3.11)
The strategy configuration was canceled because "test_analyze_project_in_root.ubuntu-latest_3_13" failed
|
|
Test analyze-project in root of repo (windows-latest, 3.13)
The operation was canceled.
|
|
Test analyze-project in root of repo (windows-latest, 3.13)
The strategy configuration was canceled because "test_analyze_project_in_root.ubuntu-latest_3_13" failed
|
|
Test analyze-project in root of repo (macos-latest, pypy3.11)
The operation was canceled.
|
|
Test analyze-project in root of repo (macos-latest, pypy3.11)
The strategy configuration was canceled because "test_analyze_project_in_root.ubuntu-latest_3_13" failed
|
|
Test analyze-project in root of repo (macos-latest, pypy3.10)
The operation was canceled.
|
|
Test analyze-project in root of repo (macos-latest, pypy3.10)
The strategy configuration was canceled because "test_analyze_project_in_root.ubuntu-latest_3_13" failed
|
|
Test analyze-project in root of repo (ubuntu-latest, pypy3.10)
The operation was canceled.
|
|
Test analyze-project in root of repo (ubuntu-latest, pypy3.10)
The strategy configuration was canceled because "test_analyze_project_in_root.ubuntu-latest_3_13" failed
|
|
Test analyze-project in root of repo (windows-latest, 3.10)
The operation was canceled.
|
|
Test analyze-project in root of repo (windows-latest, 3.10)
The strategy configuration was canceled because "test_analyze_project_in_root.ubuntu-latest_3_13" failed
|
|
Test analyze-project in root of repo (windows-latest, pypy3.11)
The operation was canceled.
|
|
Test analyze-project in root of repo (windows-latest, pypy3.11)
The strategy configuration was canceled because "test_analyze_project_in_root.ubuntu-latest_3_13" failed
|
|
Test analyze-project in root of repo (windows-latest, pypy3.10)
The operation was canceled.
|
|
Test analyze-project in root of repo (windows-latest, pypy3.10)
The strategy configuration was canceled because "test_analyze_project_in_root.ubuntu-latest_3_13" failed
|
|
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
|
|
Test setup-poetry (cache hit) (windows-latest, pypy3.11)
The operation was canceled.
|
|
Test setup-poetry (cache hit) (windows-latest, pypy3.11)
The run was canceled by @bkeryan.
|
|
Test setup-poetry (no cache) (windows-latest, 3.13)
The operation was canceled.
|
|
Test setup-poetry (no cache) (windows-latest, 3.13)
The run was canceled by @bkeryan.
|
|
Test setup-poetry (no cache) (macos-latest, pypy3.11)
The operation was canceled.
|
|
Test setup-poetry (no cache) (macos-latest, pypy3.11)
The run was canceled by @bkeryan.
|
|
Test setup-poetry (no cache) (ubuntu-latest, pypy3.10)
The operation was canceled.
|
|
Test setup-poetry (no cache) (ubuntu-latest, pypy3.10)
The run was canceled by @bkeryan.
|
|
Test setup-poetry (no cache) (ubuntu-latest, pypy3.11)
The operation was canceled.
|
|
Test setup-poetry (no cache) (ubuntu-latest, pypy3.11)
The run was canceled by @bkeryan.
|
|
Test setup-poetry (no cache) (windows-latest, pypy3.11)
The operation was canceled.
|
|
Test setup-poetry (no cache) (windows-latest, pypy3.11)
The run was canceled by @bkeryan.
|
|
Test setup-poetry (no cache) (windows-latest, pypy3.10)
The operation was canceled.
|
|
Test setup-poetry (no cache) (windows-latest, pypy3.10)
The run was canceled by @bkeryan.
|
|
Test actions
The run was canceled by @bkeryan.
|
|
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
|
|
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
|
|
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
|
|
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
|
|
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
|
|
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
|
|
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
|
|
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
|
|
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
|
|
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
|
|
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
|
|
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
|
|
Notice
The next step is expected to fail.
|
|
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
|
|
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
|
|
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
|
|
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
|
|
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
|
|
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
|
|
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
|
|
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
|
|
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
|
|
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
|
|
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
|
|
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
|
|
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
|
|
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
|
|
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
|
|
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
|
|
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
|
|
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
|
|
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
|
|
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
|
|
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
|
|
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
|
|
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
|
|
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
|
|
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
|
|
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
|
|
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
|
|
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
|
|
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
|
|
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
|
|
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
|