DEPRECATION: --no-python-version-warning is deprecated. pip 25.1 will enforce this behaviour change. A possible replacement is to remove the flag as it's a no-op. Discussion can be found at https://github.com/pypa/pip/issues/13154

DEPRECATION: --no-python-version-warning is deprecated. pip 25.1 will enforce this behaviour change. A possible replacement is to remove the flag as it's a no-op. Discussion can be found at https://github.com/pypa/pip/issues/13154

Failed to save: Failed to CreateCacheEntry: Received non-retryable error: Failed request: (409) Conflict: cache entry with the same key, version, and scope already exists

Failed to save: Failed to CreateCacheEntry: Received non-retryable error: Failed request: (409) Conflict: cache entry with the same key, version, and scope already exists

Cache save failed.

Failed to save: Failed to CreateCacheEntry: Received non-retryable error: Failed request: (409) Conflict: cache entry with the same key, version, and scope already exists

Cache save failed.

Failed to save: Failed to CreateCacheEntry: Received non-retryable error: Failed request: (409) Conflict: cache entry with the same key, version, and scope already exists

Cache save failed.

Failed to save: Failed to CreateCacheEntry: Received non-retryable error: Failed request: (409) Conflict: cache entry with the same key, version, and scope already exists

Cache save failed.

Starting action

HTTP Request: GET https://api.github.com/repos/Diaoul/subliminal "HTTP/1.1 200 OK"

Generating comment for PR

HTTP Request: GET https://api.github.com/repos/Diaoul/subliminal/contents/data.json?ref=python-coverage-comment-action-data "HTTP/1.1 200 OK"

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

HTTP Request: GET https://api.github.com/repos/Diaoul/subliminal/issues/1209/comments "HTTP/1.1 200 OK"

Adding new comment

HTTP Request: POST https://api.github.com/repos/Diaoul/subliminal/issues/1209/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).