Skip to content

Add test scenarios for analyze-project #153

Add test scenarios for analyze-project

Add test scenarios for analyze-project #153

Triggered via pull request September 28, 2025 17:45
Status Failure
Total duration 5m 26s
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 setup-python
Run CI  /  ...  /  Test check-project-version
17s
Run CI / Test actions / Test check-project-version
Run CI  /  ...  /  Test update-project-version
21s
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
3s
Run CI / Test actions / Test Results
Fit to window
Zoom out
Zoom in

Annotations

53 errors and 37 notices
Run CI / Test actions / Test analyze-project (ubuntu-latest, 3.10)
Failed to load /home/runner/work/python-actions/python-actions/./.github/actions/test_analyze_project/action.yml
Run CI / Test actions / Test analyze-project (ubuntu-latest, 3.10)
GitHub.DistributedTask.ObjectTemplating.TemplateValidationException: The template is not valid. /home/runner/work/python-actions/python-actions/./.github/actions/test_analyze_project/action.yml (Line: 19, Col: 13): Unrecognized named-value: 'github'. Located at position 1 within expression: github.sha at GitHub.DistributedTask.ObjectTemplating.TemplateValidationErrors.Check() at GitHub.Runner.Worker.ActionManifestManager.ConvertRuns(IExecutionContext executionContext, TemplateContext templateContext, TemplateToken inputsToken, String fileRelativePath, MappingToken outputs) at GitHub.Runner.Worker.ActionManifestManager.Load(IExecutionContext executionContext, String manifestFile)
Run CI / Test actions / Test analyze-project (ubuntu-latest, 3.10)
/home/runner/work/python-actions/python-actions/./.github/actions/test_analyze_project/action.yml (Line: 19, Col: 13): Unrecognized named-value: 'github'. Located at position 1 within expression: github.sha
Run CI / Test actions / Test analyze-project (ubuntu-latest, 3.9)
Failed to load /home/runner/work/python-actions/python-actions/./.github/actions/test_analyze_project/action.yml
Run CI / Test actions / Test analyze-project (ubuntu-latest, 3.9)
GitHub.DistributedTask.ObjectTemplating.TemplateValidationException: The template is not valid. /home/runner/work/python-actions/python-actions/./.github/actions/test_analyze_project/action.yml (Line: 19, Col: 13): Unrecognized named-value: 'github'. Located at position 1 within expression: github.sha at GitHub.DistributedTask.ObjectTemplating.TemplateValidationErrors.Check() at GitHub.Runner.Worker.ActionManifestManager.ConvertRuns(IExecutionContext executionContext, TemplateContext templateContext, TemplateToken inputsToken, String fileRelativePath, MappingToken outputs) at GitHub.Runner.Worker.ActionManifestManager.Load(IExecutionContext executionContext, String manifestFile)
Run CI / Test actions / Test analyze-project (ubuntu-latest, 3.9)
/home/runner/work/python-actions/python-actions/./.github/actions/test_analyze_project/action.yml (Line: 19, Col: 13): Unrecognized named-value: 'github'. Located at position 1 within expression: github.sha
Run CI / Test actions / Test analyze-project (ubuntu-latest, 3.9)
The strategy configuration was canceled because "run_ci.test_actions.test_analyze_project.ubuntu-latest_3_10" failed
Run CI / Test actions / Test analyze-project (ubuntu-latest, 3.13)
Failed to load /home/runner/work/python-actions/python-actions/./.github/actions/test_analyze_project/action.yml
Run CI / Test actions / Test analyze-project (ubuntu-latest, 3.13)
GitHub.DistributedTask.ObjectTemplating.TemplateValidationException: The template is not valid. /home/runner/work/python-actions/python-actions/./.github/actions/test_analyze_project/action.yml (Line: 19, Col: 13): Unrecognized named-value: 'github'. Located at position 1 within expression: github.sha at GitHub.DistributedTask.ObjectTemplating.TemplateValidationErrors.Check() at GitHub.Runner.Worker.ActionManifestManager.ConvertRuns(IExecutionContext executionContext, TemplateContext templateContext, TemplateToken inputsToken, String fileRelativePath, MappingToken outputs) at GitHub.Runner.Worker.ActionManifestManager.Load(IExecutionContext executionContext, String manifestFile)
Run CI / Test actions / Test analyze-project (ubuntu-latest, 3.13)
/home/runner/work/python-actions/python-actions/./.github/actions/test_analyze_project/action.yml (Line: 19, Col: 13): Unrecognized named-value: 'github'. Located at position 1 within expression: github.sha
Run CI / Test actions / Test analyze-project (ubuntu-latest, 3.13)
The strategy configuration was canceled because "run_ci.test_actions.test_analyze_project.ubuntu-latest_3_10" failed
Run CI / Test actions / Test analyze-project (ubuntu-latest, 3.12)
Failed to load /home/runner/work/python-actions/python-actions/./.github/actions/test_analyze_project/action.yml
Run CI / Test actions / Test analyze-project (ubuntu-latest, 3.12)
GitHub.DistributedTask.ObjectTemplating.TemplateValidationException: The template is not valid. /home/runner/work/python-actions/python-actions/./.github/actions/test_analyze_project/action.yml (Line: 19, Col: 13): Unrecognized named-value: 'github'. Located at position 1 within expression: github.sha at GitHub.DistributedTask.ObjectTemplating.TemplateValidationErrors.Check() at GitHub.Runner.Worker.ActionManifestManager.ConvertRuns(IExecutionContext executionContext, TemplateContext templateContext, TemplateToken inputsToken, String fileRelativePath, MappingToken outputs) at GitHub.Runner.Worker.ActionManifestManager.Load(IExecutionContext executionContext, String manifestFile)
Run CI / Test actions / Test analyze-project (macos-latest, 3.10)
The operation was canceled.
Run CI / Test actions / Test analyze-project (ubuntu-latest, 3.12)
/home/runner/work/python-actions/python-actions/./.github/actions/test_analyze_project/action.yml (Line: 19, Col: 13): Unrecognized named-value: 'github'. Located at position 1 within expression: github.sha
Run CI / Test actions / Test analyze-project (ubuntu-latest, 3.12)
The strategy configuration was canceled because "run_ci.test_actions.test_analyze_project.ubuntu-latest_3_10" failed
Run CI / Test actions / Test analyze-project (macos-latest, 3.10)
The strategy configuration was canceled because "run_ci.test_actions.test_analyze_project.ubuntu-latest_3_10" failed
Run CI / Test actions / Test analyze-project (macos-latest, 3.9)
The operation was canceled.
Run CI / Test actions / Test analyze-project (macos-latest, 3.9)
The strategy configuration was canceled because "run_ci.test_actions.test_analyze_project.ubuntu-latest_3_10" failed
Run CI / Test actions / Test analyze-project (macos-latest, pypy3.10)
The operation was canceled.
Run CI / Test actions / Test analyze-project (macos-latest, pypy3.10)
The strategy configuration was canceled because "run_ci.test_actions.test_analyze_project.ubuntu-latest_3_10" failed
Run CI / Test actions / Test analyze-project (windows-latest, 3.9)
The strategy configuration was canceled because "run_ci.test_actions.test_analyze_project.ubuntu-latest_3_10" failed
Run CI / Test actions / Test analyze-project (macos-latest, 3.11)
Failed to load /Users/runner/work/python-actions/python-actions/./.github/actions/test_analyze_project/action.yml
Run CI / Test actions / Test analyze-project (macos-latest, 3.11)
GitHub.DistributedTask.ObjectTemplating.TemplateValidationException: The template is not valid. /Users/runner/work/python-actions/python-actions/./.github/actions/test_analyze_project/action.yml (Line: 19, Col: 13): Unrecognized named-value: 'github'. Located at position 1 within expression: github.sha at GitHub.DistributedTask.ObjectTemplating.TemplateValidationErrors.Check() at GitHub.Runner.Worker.ActionManifestManager.ConvertRuns(IExecutionContext executionContext, TemplateContext templateContext, TemplateToken inputsToken, String fileRelativePath, MappingToken outputs) at GitHub.Runner.Worker.ActionManifestManager.Load(IExecutionContext executionContext, String manifestFile)
Run CI / Test actions / Test analyze-project (macos-latest, 3.11)
/Users/runner/work/python-actions/python-actions/./.github/actions/test_analyze_project/action.yml (Line: 19, Col: 13): Unrecognized named-value: 'github'. Located at position 1 within expression: github.sha
Run CI / Test actions / Test analyze-project (macos-latest, 3.11)
The strategy configuration was canceled because "run_ci.test_actions.test_analyze_project.ubuntu-latest_3_10" failed
Run CI / Test actions / Test analyze-project (macos-latest, pypy3.11)
The operation was canceled.
Run CI / Test actions / Test analyze-project (macos-latest, pypy3.11)
The strategy configuration was canceled because "run_ci.test_actions.test_analyze_project.ubuntu-latest_3_10" failed
Run CI / Test actions / Test analyze-project (windows-latest, 3.13)
The strategy configuration was canceled because "run_ci.test_actions.test_analyze_project.ubuntu-latest_3_10" failed
Run CI / Test actions / Test analyze-project (ubuntu-latest, pypy3.10)
The operation was canceled.
Run CI / Test actions / Test analyze-project (ubuntu-latest, pypy3.10)
The strategy configuration was canceled because "run_ci.test_actions.test_analyze_project.ubuntu-latest_3_10" failed
Run CI / Test actions / Test analyze-project (macos-latest, 3.13)
The operation was canceled.
Run CI / Test actions / Test analyze-project (macos-latest, 3.13)
The strategy configuration was canceled because "run_ci.test_actions.test_analyze_project.ubuntu-latest_3_10" failed
Run CI / Test actions / Test analyze-project (ubuntu-latest, 3.11)
The operation was canceled.
Run CI / Test actions / Test analyze-project (ubuntu-latest, 3.11)
The strategy configuration was canceled because "run_ci.test_actions.test_analyze_project.ubuntu-latest_3_10" failed
Run CI / Test actions / Test analyze-project (macos-latest, 3.12)
The operation was canceled.
Run CI / Test actions / Test analyze-project (macos-latest, 3.12)
The strategy configuration was canceled because "run_ci.test_actions.test_analyze_project.ubuntu-latest_3_10" failed
Run CI / Test actions / Test analyze-project (ubuntu-latest, pypy3.11)
The operation was canceled.
Run CI / Test actions / Test analyze-project (ubuntu-latest, pypy3.11)
The strategy configuration was canceled because "run_ci.test_actions.test_analyze_project.ubuntu-latest_3_10" failed
Run CI / Test actions / Test analyze-project (windows-latest, 3.11)
The operation was canceled.
Run CI / Test actions / Test analyze-project (windows-latest, 3.11)
The strategy configuration was canceled because "run_ci.test_actions.test_analyze_project.ubuntu-latest_3_10" failed
Run CI / Test actions / Test analyze-project (windows-latest, pypy3.10)
The strategy configuration was canceled because "run_ci.test_actions.test_analyze_project.ubuntu-latest_3_10" failed
Run CI / Test actions / Test analyze-project (windows-latest, 3.10)
The operation was canceled.
Run CI / Test actions / Test analyze-project (windows-latest, 3.10)
The strategy configuration was canceled because "run_ci.test_actions.test_analyze_project.ubuntu-latest_3_10" failed
Run CI / Test actions / Test analyze-project (windows-latest, 3.12)
The operation was canceled.
Run CI / Test actions / Test analyze-project (windows-latest, 3.12)
The strategy configuration was canceled because "run_ci.test_actions.test_analyze_project.ubuntu-latest_3_10" failed
Run CI / Test actions / Test analyze-project (windows-latest, pypy3.11)
The strategy configuration was canceled because "run_ci.test_actions.test_analyze_project.ubuntu-latest_3_10" failed
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 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 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, 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.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 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, 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.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.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.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.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
Notice
The next step is expected to fail.
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-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-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.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 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, 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, 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-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 (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 (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-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-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, 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, 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.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 (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 (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 (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 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 (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