Failed to CreateArtifact: Received non-retryable error: Failed request: (409) Conflict: an artifact with this name already exists on the workflow run

Failed to CreateArtifact: Received non-retryable error: Failed request: (409) Conflict: an artifact with this name already exists on the workflow run

The job was canceled because "_3_10" failed.

Failed to CreateArtifact: Received non-retryable error: Failed request: (409) Conflict: an artifact with this name already exists on the workflow run

The following actions uses node12 which is deprecated and will be forced to run on node16: actions/[email protected]. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/

The following actions uses Node.js version which is deprecated and will be forced to run on node20: actions/checkout@v3, actions/[email protected]. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/

The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/

The following actions uses node12 which is deprecated and will be forced to run on node16: actions/[email protected]. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/

The following actions uses Node.js version which is deprecated and will be forced to run on node20: actions/checkout@v3, actions/[email protected]. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/

The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/

The following actions uses node12 which is deprecated and will be forced to run on node16: actions/[email protected]. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/

The following actions uses Node.js version which is deprecated and will be forced to run on node20: actions/checkout@v3, actions/[email protected]. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/

The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/

The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/

Starting action

HTTP Request: GET https://api.github.com/repos/adamghill/django-unicorn "HTTP/1.1 200 OK"

Generating comment for PR

HTTP Request: GET https://api.github.com/repos/adamghill/django-unicorn/contents/data.json?ref=python-coverage-comment-action-data "HTTP/1.1 404 Not Found"

HTTP Request: GET https://api.github.com/user "HTTP/1.1 403 Forbidden"

HTTP Request: GET https://api.github.com/repos/adamghill/django-unicorn/issues/709/comments "HTTP/1.1 200 OK"

Adding new comment

HTTP Request: POST https://api.github.com/repos/adamghill/django-unicorn/issues/709/comments "HTTP/1.1 403 Forbidden"

Cannot post comment. This is probably because this is an external PR, so it's expected. Ensure you have an additional `workflow_run` step configured as explained in the documentation (or alternatively, give up on PR comments for external PRs).

Ending action

Starting action

HTTP Request: GET https://api.github.com/repos/adamghill/django-unicorn "HTTP/1.1 200 OK"

Generating comment for PR

HTTP Request: GET https://api.github.com/repos/adamghill/django-unicorn/contents/data.json?ref=python-coverage-comment-action-data "HTTP/1.1 404 Not Found"

HTTP Request: GET https://api.github.com/user "HTTP/1.1 403 Forbidden"

HTTP Request: GET https://api.github.com/repos/adamghill/django-unicorn/issues/709/comments "HTTP/1.1 200 OK"

Adding new comment

HTTP Request: POST https://api.github.com/repos/adamghill/django-unicorn/issues/709/comments "HTTP/1.1 403 Forbidden"

Cannot post comment. This is probably because this is an external PR, so it's expected. Ensure you have an additional `workflow_run` step configured as explained in the documentation (or alternatively, give up on PR comments for external PRs).

Ending action

Starting action

HTTP Request: GET https://api.github.com/repos/adamghill/django-unicorn "HTTP/1.1 200 OK"

Generating comment for PR

HTTP Request: GET https://api.github.com/repos/adamghill/django-unicorn/contents/data.json?ref=python-coverage-comment-action-data "HTTP/1.1 404 Not Found"

HTTP Request: GET https://api.github.com/user "HTTP/1.1 403 Forbidden"

HTTP Request: GET https://api.github.com/repos/adamghill/django-unicorn/issues/709/comments "HTTP/1.1 200 OK"

Adding new comment

HTTP Request: POST https://api.github.com/repos/adamghill/django-unicorn/issues/709/comments "HTTP/1.1 403 Forbidden"

Cannot post comment. This is probably because this is an external PR, so it's expected. Ensure you have an additional `workflow_run` step configured as explained in the documentation (or alternatively, give up on PR comments for external PRs).

Ending action

Starting action

HTTP Request: GET https://api.github.com/repos/adamghill/django-unicorn "HTTP/1.1 200 OK"

Generating comment for PR

HTTP Request: GET https://api.github.com/repos/adamghill/django-unicorn/contents/data.json?ref=python-coverage-comment-action-data "HTTP/1.1 404 Not Found"

HTTP Request: GET https://api.github.com/user "HTTP/1.1 403 Forbidden"

HTTP Request: GET https://api.github.com/repos/adamghill/django-unicorn/issues/709/comments "HTTP/1.1 200 OK"

Adding new comment

HTTP Request: POST https://api.github.com/repos/adamghill/django-unicorn/issues/709/comments "HTTP/1.1 403 Forbidden"

Cannot post comment. This is probably because this is an external PR, so it's expected. Ensure you have an additional `workflow_run` step configured as explained in the documentation (or alternatively, give up on PR comments for external PRs).