Add test scenarios for analyze-project #151
Triggered via pull request
September 28, 2025 17:23
dixonjoel
Status
Cancelled
Total duration
4m 22s
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
23s
Run CI
/
...
/
Test update-project-version
26s
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
Annotations
60 errors and 37 notices
|
Run CI / Test actions / Test analyze-project (ubuntu-latest, 3.11)
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.11)
System.FormatException: Input string was not in a correct format. Failure to parse near offset 136. Expected an ASCII digit.
at System.Text.ValueStringBuilder.AppendFormatHelper(IFormatProvider provider, String format, ReadOnlySpan`1 args)
at System.String.FormatHelper(IFormatProvider provider, String format, ReadOnlySpan`1 args)
at System.String.Format(IFormatProvider provider, String format, Object[] args)
at GitHub.Runner.Worker.TemplateTraceWriter.Error(String format, Object[] args)
at GitHub.DistributedTask.ObjectTemplating.TemplateContext.Error(Nullable`1 fileId, Nullable`1 line, Nullable`1 column, String message)
at GitHub.DistributedTask.ObjectTemplating.TemplateContext.Error(TemplateToken value, String message)
at GitHub.DistributedTask.Pipelines.ObjectTemplating.PipelineTemplateConverter.ConvertToStep(TemplateContext context, TemplateToken stepsItem, ReferenceNameBuilder nameBuilder)
at GitHub.DistributedTask.Pipelines.ObjectTemplating.PipelineTemplateConverter.ConvertToSteps(TemplateContext context, TemplateToken steps)
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.11)
/home/runner/work/python-actions/python-actions/./.github/actions/test_analyze_project/action.yml (Line: 19, Col: 13): Expected format {org}/{repo}[/path]@ref. Actual '../../analyze-project'
|
|
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)
System.FormatException: Input string was not in a correct format. Failure to parse near offset 136. Expected an ASCII digit.
at System.Text.ValueStringBuilder.AppendFormatHelper(IFormatProvider provider, String format, ReadOnlySpan`1 args)
at System.String.FormatHelper(IFormatProvider provider, String format, ReadOnlySpan`1 args)
at System.String.Format(IFormatProvider provider, String format, Object[] args)
at GitHub.Runner.Worker.TemplateTraceWriter.Error(String format, Object[] args)
at GitHub.DistributedTask.ObjectTemplating.TemplateContext.Error(Nullable`1 fileId, Nullable`1 line, Nullable`1 column, String message)
at GitHub.DistributedTask.ObjectTemplating.TemplateContext.Error(TemplateToken value, String message)
at GitHub.DistributedTask.Pipelines.ObjectTemplating.PipelineTemplateConverter.ConvertToStep(TemplateContext context, TemplateToken stepsItem, ReferenceNameBuilder nameBuilder)
at GitHub.DistributedTask.Pipelines.ObjectTemplating.PipelineTemplateConverter.ConvertToSteps(TemplateContext context, TemplateToken steps)
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): Expected format {org}/{repo}[/path]@ref. Actual '../../analyze-project'
|
|
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_11" failed
|
|
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)
System.FormatException: Input string was not in a correct format. Failure to parse near offset 136. Expected an ASCII digit.
at System.Text.ValueStringBuilder.AppendFormatHelper(IFormatProvider provider, String format, ReadOnlySpan`1 args)
at System.String.FormatHelper(IFormatProvider provider, String format, ReadOnlySpan`1 args)
at System.String.Format(IFormatProvider provider, String format, Object[] args)
at GitHub.Runner.Worker.TemplateTraceWriter.Error(String format, Object[] args)
at GitHub.DistributedTask.ObjectTemplating.TemplateContext.Error(Nullable`1 fileId, Nullable`1 line, Nullable`1 column, String message)
at GitHub.DistributedTask.ObjectTemplating.TemplateContext.Error(TemplateToken value, String message)
at GitHub.DistributedTask.Pipelines.ObjectTemplating.PipelineTemplateConverter.ConvertToStep(TemplateContext context, TemplateToken stepsItem, ReferenceNameBuilder nameBuilder)
at GitHub.DistributedTask.Pipelines.ObjectTemplating.PipelineTemplateConverter.ConvertToSteps(TemplateContext context, TemplateToken steps)
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): Expected format {org}/{repo}[/path]@ref. Actual '../../analyze-project'
|
|
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_11" 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)
System.FormatException: Input string was not in a correct format. Failure to parse near offset 137. Expected an ASCII digit.
at System.Text.ValueStringBuilder.AppendFormatHelper(IFormatProvider provider, String format, ReadOnlySpan`1 args)
at System.String.FormatHelper(IFormatProvider provider, String format, ReadOnlySpan`1 args)
at System.String.Format(IFormatProvider provider, String format, Object[] args)
at GitHub.Runner.Worker.TemplateTraceWriter.Error(String format, Object[] args)
at GitHub.DistributedTask.ObjectTemplating.TemplateContext.Error(Nullable`1 fileId, Nullable`1 line, Nullable`1 column, String message)
at GitHub.DistributedTask.ObjectTemplating.TemplateContext.Error(TemplateToken value, String message)
at GitHub.DistributedTask.Pipelines.ObjectTemplating.PipelineTemplateConverter.ConvertToStep(TemplateContext context, TemplateToken stepsItem, ReferenceNameBuilder nameBuilder)
at GitHub.DistributedTask.Pipelines.ObjectTemplating.PipelineTemplateConverter.ConvertToSteps(TemplateContext context, TemplateToken steps)
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): Expected format {org}/{repo}[/path]@ref. Actual '../../analyze-project'
|
|
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_11" 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_11" 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_11" 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_11" failed
|
|
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 (macos-latest, pypy3.11)
The operation was canceled.
|
|
Run CI / Test actions / Test analyze-project (ubuntu-latest, 3.10)
System.FormatException: Input string was not in a correct format. Failure to parse near offset 136. Expected an ASCII digit.
at System.Text.ValueStringBuilder.AppendFormatHelper(IFormatProvider provider, String format, ReadOnlySpan`1 args)
at System.String.FormatHelper(IFormatProvider provider, String format, ReadOnlySpan`1 args)
at System.String.Format(IFormatProvider provider, String format, Object[] args)
at GitHub.Runner.Worker.TemplateTraceWriter.Error(String format, Object[] args)
at GitHub.DistributedTask.ObjectTemplating.TemplateContext.Error(Nullable`1 fileId, Nullable`1 line, Nullable`1 column, String message)
at GitHub.DistributedTask.ObjectTemplating.TemplateContext.Error(TemplateToken value, String message)
at GitHub.DistributedTask.Pipelines.ObjectTemplating.PipelineTemplateConverter.ConvertToStep(TemplateContext context, TemplateToken stepsItem, ReferenceNameBuilder nameBuilder)
at GitHub.DistributedTask.Pipelines.ObjectTemplating.PipelineTemplateConverter.ConvertToSteps(TemplateContext context, TemplateToken steps)
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, pypy3.11)
The strategy configuration was canceled because "run_ci.test_actions.test_analyze_project.ubuntu-latest_3_11" failed
|
|
Run CI / Test actions / Test analyze-project (macos-latest, pypy3.10)
The operation was canceled.
|
|
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): Expected format {org}/{repo}[/path]@ref. Actual '../../analyze-project'
|
|
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_11" failed
|
|
Run CI / Test actions / Test analyze-project (ubuntu-latest, 3.10)
The strategy configuration was canceled because "run_ci.test_actions.test_analyze_project.ubuntu-latest_3_11" 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_11" failed
|
|
Run CI / Test actions / Test analyze-project (macos-latest, 3.10)
The operation was canceled.
|
|
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_11" failed
|
|
Run CI / Test actions / Test analyze-project (ubuntu-latest, 3.12)
The operation was canceled.
|
|
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_11" failed
|
|
Run CI / Test actions / Test analyze-project (windows-latest, 3.9)
The operation was canceled.
|
|
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_11" failed
|
|
Run CI / Test actions / Test analyze-project (windows-latest, 3.12)
A task 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_11" 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_11" 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_11" failed
|
|
Run CI / Test actions / Test analyze-project (windows-latest, pypy3.10)
The operation was canceled.
|
|
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_11" 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_11" failed
|
|
Run CI / Test actions / Test analyze-project (windows-latest, 3.13)
The operation was canceled.
|
|
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_11" failed
|
|
Run CI / Test actions / Test analyze-project (windows-latest, pypy3.11)
The operation was canceled.
|
|
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_11" 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-poetry (no cache) (ubuntu-latest, pypy3.11)
The operation was canceled.
|
|
Run CI / Test actions / Test setup-poetry (no cache) (ubuntu-latest, pypy3.11)
Canceling since a higher priority waiting request for PR-36 exists
|
|
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)
Canceling since a higher priority waiting request for PR-36 exists
|
|
PR
Canceling since a higher priority waiting request for PR-36 exists
|
|
PR
Canceling since a higher priority waiting request for PR-36 exists
|
|
PR
Canceling since a higher priority waiting request for PR-36 exists
|
|
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, 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.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.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.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.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-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-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
|
|
Notice
The next step is expected to fail.
|
|
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.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.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.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.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.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.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.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 (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-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.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.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.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, 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.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, 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
|