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

Cache not found for keys: baipp-3f90074aa1ae051ed85c628263149fee339611d3ee83927a5845d19345dcfa4f

Cache not found for keys: setup-python-Linux-x64-24.04-Ubuntu-python-3.12.9-pip-eaa80964ede9ef108b58505fc8b481066f772685dd059709d4ad54376ac121f6, setup-python-Linux-x64-24.04-Ubuntu-python-3.12.9-pip

Cache not found for keys: pre-commit-3|/opt/hostedtoolcache/Python/3.12.9/x64|d0a57d6e755495e6f78e3cf2da1b6cf5d49c277e24dee3b490c761a1c80d8a2a

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 not found for keys: setup-python-Linux-x64-24.04-Ubuntu-python-3.12.9-pip-eaa80964ede9ef108b58505fc8b481066f772685dd059709d4ad54376ac121f6, setup-python-Linux-x64-24.04-Ubuntu-python-3.12.9-pip

Cache not found for keys: uv-Linux-CI-coverage-eaa80964ede9ef108b58505fc8b481066f772685dd059709d4ad54376ac121f6-07

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/1204/comments "HTTP/1.1 200 OK"

Adding new comment

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