Skip to content
Test and Optionally Publish

Always Upgrade on Init #278

Sign in to view logs

Always Upgrade on Init

Always Upgrade on Init #278

Triggered via pull request August 30, 2024 15:19
@jconstance-amplifyjconstance-amplify
opened #191
always_upgrade
Status Failure
Total duration 53s
Artifacts –

test-build-publish.yml

on: pull_request
Matrix: Check code against linter/unit tests
Verify that version was updated
3s
Verify that version was updated
Build and publish Python distributions
0s
Build and publish Python distributions
Fit to window
Zoom out
Zoom in

Annotations

7 errors and 2 warnings
Check code against linter/unit tests (3.11)
Process completed with exit code 1.
Check code against linter/unit tests (3.8)
The job was canceled because "_3_11" failed.
Check code against linter/unit tests (3.8)
The operation was canceled.
Check code against linter/unit tests (3.9)
The job was canceled because "_3_11" failed.
Check code against linter/unit tests (3.9)
The operation was canceled.
Check code against linter/unit tests (3.10)
The job was canceled because "_3_11" failed.
Check code against linter/unit tests (3.10)
The operation was canceled.
Check code against linter/unit tests (3.11)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-python@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Check code against linter/unit tests (3.11)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-python@v2. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/