feat: upgrade from Python 3.8 to Python 3.11 (#189) #680
Annotations
1 error, 9 warnings, and 7 notices
Tests (ubuntu-20.04, 3.11, 10, django42)
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 '('git', 'push', 'origin', 'python-coverage-comment-action-data')' returned non-zero exit status 128.
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(
^^^^
File "/workdir/coverage_comment/subprocess.py", line 36, in run
raise SubProcessError("\n".join([exc.stderr, exc.stdout])) from exc
coverage_comment.subprocess.SubProcessError: fatal: could not read Username for 'https://github.com': No such device or address
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 88, in action
return save_coverage_data_files(
^^^^^^^^^^^^^^^^^^^^^^^^^
File "/workdir/coverage_comment/main.py", line 410, in save_coverage_data_files
storage.commit_operations(
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
|
Tests (ubuntu-20.04, 3.11, 10, rst_validation)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-python@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
Tests (ubuntu-20.04, 3.11, 10, rst_validation)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-python@v2. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
Tests (ubuntu-20.04, 3.11, 10, quality)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-python@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
Tests (ubuntu-20.04, 3.11, 10, quality)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-python@v2. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
Tests (ubuntu-20.04, 3.11, 10, pii_check)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-python@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
Tests (ubuntu-20.04, 3.11, 10, pii_check)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-python@v2. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
Tests (ubuntu-20.04, 3.11, 10, django42)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-python@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
Tests (ubuntu-20.04, 3.11, 10, django42)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-python@v2. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
Tests (ubuntu-20.04, 3.11, 10, django42)
Unexpected input(s) 'uses', 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']
|
Tests (ubuntu-20.04, 3.11, 10, django42)
Starting action
|
Tests (ubuntu-20.04, 3.11, 10, django42)
HTTP Request: GET https://api.github.com/repos/edx/edx-name-affirmation "HTTP/1.1 200 OK"
|
Tests (ubuntu-20.04, 3.11, 10, django42)
Computing coverage files & badge
|
Tests (ubuntu-20.04, 3.11, 10, django42)
HTTP Request: GET https://img.shields.io/static/v1?label=Coverage&message=100%25&color=brightgreen "HTTP/1.1 200 OK"
|
Tests (ubuntu-20.04, 3.11, 10, django42)
Generating HTML coverage report
|
Tests (ubuntu-20.04, 3.11, 10, django42)
Creating branch python-coverage-comment-action-data
|
Tests (ubuntu-20.04, 3.11, 10, django42)
Saving coverage files
|