Critical error. This error possibly occurred because the permissions of the workflow are set incorrectly. You can see the correct setting of permissions here: https://github.com/py-cov-action/python-coverage-comment-action#basic-usage Otherwise please look for open issues or open one in https://github.com/py-cov-action/python-coverage-comment-action/ Traceback (most recent call last): File "/workdir/coverage_comment/subprocess.py", line 22, in run return subprocess.run( ~~~~~~~~~~~~~~^ args, ^^^^^ ...<6 lines>... **kwargs, ^^^^^^^^^ ).stdout ^ File "/usr/local/lib/python3.14/subprocess.py", line 577, in run raise CalledProcessError(retcode, process.args, output=stdout, stderr=stderr) subprocess.CalledProcessError: Command '('git', 'push', 'origin', 'python-coverage-comment-action-data')' returned non-zero exit status 1. The above exception was the direct cause of the following exception: Traceback (most recent call last): File "/workdir/coverage_comment/subprocess.py", line 65, in _git return run( "git", ...<3 lines>... **kwargs, ) File "/workdir/coverage_comment/subprocess.py", line 36, in run raise SubProcessError("\n".join([exc.stderr, exc.stdout])) from exc coverage_comment.subprocess.SubProcessError: To https://github.com/Not-Diamond/notdiamond-python ! [rejected] python-coverage-comment-action-data -> python-coverage-comment-action-data (fetch first) error: failed to push some refs to 'https://github.com/Not-Diamond/notdiamond-python' hint: Updates were rejected because the remote contains work that you do not hint: have locally. This is usually caused by another repository pushing to hint: the same ref. If you want to integrate the remote changes, use hint: 'git pull' before pushing again. hint: See the 'Note about fast-forwards' in 'git push --help' for details. The above exception was the direct cause of the following exception: Traceback (most recent call last): File "/workdir/coverage_comment/main.py", line 46, in main exit_code = action( config=config, ...<2 lines>... git=git, ) File "/workdir/coverage_comment/main.py", line 93, in action return save_coverage_data_files( config=config, ...<2 lines>... repo_info=repo_info, ) File "/workdir/coverage_comment/main.py", line 452, in save_coverage_data_files storage.commit_operations( ~~~~~~~~~~~~~~~~~~~~~~~~~^ operations=operations, ^^^^^^^^^^^^^^^^^^^^^^ git=git, ^^^^^^^^ branch=config.FINAL_COVERAGE_DATA_BRANCH, ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ ) ^ File "/workdir/coverage_comment/storage.py", line 110, in commit_operations git.push("origin", branch) ~~~~~~~~^^^^^^^^^^^^^^^^^^ File "/workdir/coverage_comment/subprocess.py", line 73, in _git raise GitError from exc coverage_comment.subprocess.GitError

Failed to save: "/usr/bin/tar" failed with error: The process '/usr/bin/tar' failed with exit code 2

Failed to save: "/usr/bin/tar" failed with error: The process '/usr/bin/tar' failed with exit code 2

Saving coverage files

Generating HTML coverage report

HTTP Request: GET https://img.shields.io/static/v1?label=Coverage&message=87%25&color=brightgreen "HTTP/1.1 200 OK"

Computing coverage files & badge

HTTP Request: GET https://api.github.com/repos/Not-Diamond/notdiamond-python "HTTP/1.1 200 OK"

Starting action

Ending action

You can browse the full coverage report at: https://htmlpreview.github.io/?https://github.com/Not-Diamond/notdiamond-python/blob/python-coverage-comment-action-data/htmlcov/index.html You can use the following URLs to display your badge: - Badge SVG available at: https://raw.githubusercontent.com/Not-Diamond/notdiamond-python/python-coverage-comment-action-data/badge.svg - Badge from shields endpoint is easier to customize but doesn't work with private repo: https://img.shields.io/endpoint?url=https://raw.githubusercontent.com/Not-Diamond/notdiamond-python/python-coverage-comment-action-data/endpoint.json - Badge from shields dynamic url (less useful but you never know): https://img.shields.io/badge/dynamic/json?color=brightgreen&label=coverage&query=%24.message&url=https%3A%2F%2Fraw.githubusercontent.com%2FNot-Diamond%2Fnotdiamond-python%2Fpython-coverage-comment-action-data%2Fendpoint.json See more details and ready-to-copy-paste-markdown at: https://github.com/Not-Diamond/notdiamond-python/tree/python-coverage-comment-action-data

Files saved

Saving coverage files

Generating HTML coverage report

HTTP Request: GET https://img.shields.io/static/v1?label=Coverage&message=87%25&color=brightgreen "HTTP/1.1 200 OK"

Computing coverage files & badge

HTTP Request: GET https://api.github.com/repos/Not-Diamond/notdiamond-python "HTTP/1.1 200 OK"

Starting action

Ending action

You can browse the full coverage report at: https://htmlpreview.github.io/?https://github.com/Not-Diamond/notdiamond-python/blob/python-coverage-comment-action-data/htmlcov/index.html You can use the following URLs to display your badge: - Badge SVG available at: https://raw.githubusercontent.com/Not-Diamond/notdiamond-python/python-coverage-comment-action-data/badge.svg - Badge from shields endpoint is easier to customize but doesn't work with private repo: https://img.shields.io/endpoint?url=https://raw.githubusercontent.com/Not-Diamond/notdiamond-python/python-coverage-comment-action-data/endpoint.json - Badge from shields dynamic url (less useful but you never know): https://img.shields.io/badge/dynamic/json?color=brightgreen&label=coverage&query=%24.message&url=https%3A%2F%2Fraw.githubusercontent.com%2FNot-Diamond%2Fnotdiamond-python%2Fpython-coverage-comment-action-data%2Fendpoint.json See more details and ready-to-copy-paste-markdown at: https://github.com/Not-Diamond/notdiamond-python/tree/python-coverage-comment-action-data

Files saved

Saving coverage files

Generating HTML coverage report

HTTP Request: GET https://img.shields.io/static/v1?label=Coverage&message=86%25&color=brightgreen "HTTP/1.1 200 OK"

Computing coverage files & badge

HTTP Request: GET https://api.github.com/repos/Not-Diamond/notdiamond-python "HTTP/1.1 200 OK"