Skip to content
PR

Add test scenarios for analyze-project #159

Sign in to view logs

Add test scenarios for analyze-project

Add test scenarios for analyze-project #159

Triggered via pull request September 28, 2025 19:02
@dixonjoeldixonjoel
synchronize #36
users/jdixon/analyze-project-tests
Status Success
Total duration 6m 4s
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
24s
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

86 errors and 100 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.12)
Process completed with exit code 1.
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.11)
Process completed with exit code 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 (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 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.9)
Process completed with exit code 1.
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 (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 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.11)
Process completed with exit code 1.
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 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 (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 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 (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 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 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, 3.10)
Process completed with exit code 1.
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, pypy3.11)
Process completed with exit code 1.
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 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.12)
Process completed with exit code 1.
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.9)
Process completed with exit code 1.
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.11)
Process completed with exit code 1.
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 (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 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 (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 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, 3.10)
Process completed with exit code 1.
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, pypy3.10)
Process completed with exit code 1.
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 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 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.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, 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-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.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.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.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, 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 Success
Previous step failed as expected.
Test Success
Previous step failed as expected.
Test Success
Previous step failed as expected.
Test Success
Previous step failed as expected.
Test Success
Previous step failed as expected.
Test Success
Previous step failed as expected.
Test Success
Previous step failed as expected.
Test Success
Previous step failed as expected.
Test Success
Previous step failed as expected.
Test Success
Previous step failed as expected.
Test Success
Previous step failed as expected.
Test Success
Previous step failed as expected.
Test Success
Previous step failed as expected.
Test Success
Previous step failed as expected.
Test Success
Previous step failed as expected.
Test Success
Previous step failed as expected.
Test Success
Previous step failed as expected.
Test Success
Previous step failed as expected.
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.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 Success
Previous step failed as expected.
Test Success
Previous step failed as expected.
Test Success
Previous step failed as expected.
Test Success
Previous step failed as expected.
Test Success
Previous step failed as expected.
Test Success
Previous step failed as expected.
Test Success
Previous step failed as expected.
Test Success
Previous step failed as expected.
Test Success
Previous step failed as expected.
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
Test Success
Previous step failed as expected.
Test Success
Previous step failed as expected.
Test Success
Previous step failed as expected.
Test Success
Previous step failed as expected.
Test Success
Previous step failed as expected.
Test Success
Previous step failed as expected.
Test Success
Previous step failed as expected.
Test Success
Previous step failed as expected.
Test Success
Previous step failed as expected.
Test Success
Previous step failed as expected.
Test Success
Previous step failed as expected.
Test Success
Previous step failed as expected.
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
Test Success
Previous step failed as expected.
Test Success
Previous step failed as expected.
Test Success
Previous step failed as expected.
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
Test Success
Previous step failed as expected.
Test Success
Previous step failed as expected.
Test Success
Previous step failed as expected.
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
Test Success
Previous step failed as expected.
Test Success
Previous step failed as expected.
Test Success
Previous step failed as expected.
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 (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 (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 Success
Previous step failed as expected.
Test Success
Previous step failed as expected.
Test Success
Previous step failed as expected.
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.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 Success
Previous step failed as expected.
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
Test Success
Previous step failed as expected.
Test Success
Previous step failed as expected.
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-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 Success
Previous step failed as expected.
Test Success
Previous step failed as expected.
Test Success
Previous step failed as expected.
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.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.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 (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.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
Test Success
Previous step failed as expected.
Test Success
Previous step failed as expected.
Test Success
Previous step failed as expected.
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-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 Success
Previous step failed as expected.
Test Success
Previous step failed as expected.
Test Success
Previous step failed as expected.
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, 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