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( ^^^^^^^^^^^^^^^ File "/usr/local/lib/python3.12/subprocess.py", line 571, in run raise CalledProcessError(retcode, process.args, subprocess.CalledProcessError: Command '('coverage', 'json', '-o', '-')' 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/main.py", line 44, in main exit_code = action( ^^^^^^^ File "/workdir/coverage_comment/main.py", line 96, in action return process_pr( ^^^^^^^^^^^ File "/workdir/coverage_comment/main.py", line 127, in process_pr _, coverage = coverage_module.get_coverage_info( ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/workdir/coverage_comment/coverage.py", line 99, in get_coverage_info subprocess.run("coverage", "json", "-o", "-", path=coverage_path) File "/workdir/coverage_comment/subprocess.py", line 36, in run raise SubProcessError("\n".join([exc.stderr, exc.stdout])) from exc coverage_comment.subprocess.SubProcessError: No data to report.

The job was canceled because "_3_11" failed.

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( ^^^^^^^^^^^^^^^ File "/usr/local/lib/python3.12/subprocess.py", line 571, in run raise CalledProcessError(retcode, process.args, subprocess.CalledProcessError: Command '('coverage', 'json', '-o', '-')' 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/main.py", line 44, in main exit_code = action( ^^^^^^^ File "/workdir/coverage_comment/main.py", line 96, in action return process_pr( ^^^^^^^^^^^ File "/workdir/coverage_comment/main.py", line 127, in process_pr _, coverage = coverage_module.get_coverage_info( ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/workdir/coverage_comment/coverage.py", line 99, in get_coverage_info subprocess.run("coverage", "json", "-o", "-", path=coverage_path) File "/workdir/coverage_comment/subprocess.py", line 36, in run raise SubProcessError("\n".join([exc.stderr, exc.stdout])) from exc coverage_comment.subprocess.SubProcessError: No data to report.

The job was canceled because "_3_11" failed.

The operation was canceled.

The job was canceled because "_3_11" failed.

The operation was canceled.

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/

Unexpected input(s) 'COVERAGE_FILE', valid inputs are ['entryPoint', 'args', 'GITHUB_TOKEN', 'GITHUB_PR_RUN_ID', 'COMMENT_TEMPLATE', 'COVERAGE_DATA_BRANCH', 'COVERAGE_PATH', 'COMMENT_ARTIFACT_NAME', 'COMMENT_FILENAME', 'SUBPROJECT_ID', 'MINIMUM_GREEN', 'MINIMUM_ORANGE', 'MAX_FILES_IN_COMMENT', 'MERGE_COVERAGE_FILES', 'ANNOTATE_MISSING_LINES', 'ANNOTATION_TYPE', 'VERBOSE']

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/

Unexpected input(s) 'COVERAGE_FILE', valid inputs are ['entryPoint', 'args', 'GITHUB_TOKEN', 'GITHUB_PR_RUN_ID', 'COMMENT_TEMPLATE', 'COVERAGE_DATA_BRANCH', 'COVERAGE_PATH', 'COMMENT_ARTIFACT_NAME', 'COMMENT_FILENAME', 'SUBPROJECT_ID', 'MINIMUM_GREEN', 'MINIMUM_ORANGE', 'MAX_FILES_IN_COMMENT', 'MERGE_COVERAGE_FILES', 'ANNOTATE_MISSING_LINES', 'ANNOTATION_TYPE', 'VERBOSE']

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/

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/

Unexpected input(s) 'COVERAGE_FILE', valid inputs are ['entryPoint', 'args', 'GITHUB_TOKEN', 'GITHUB_PR_RUN_ID', 'COMMENT_TEMPLATE', 'COVERAGE_DATA_BRANCH', 'COVERAGE_PATH', 'COMMENT_ARTIFACT_NAME', 'COMMENT_FILENAME', 'SUBPROJECT_ID', 'MINIMUM_GREEN', 'MINIMUM_ORANGE', 'MAX_FILES_IN_COMMENT', 'MERGE_COVERAGE_FILES', 'ANNOTATE_MISSING_LINES', 'ANNOTATION_TYPE', 'VERBOSE']

Starting action

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

Generating comment for PR

Starting action

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