Move tests into tests directory #138
rettinghausAnnotations
13 errors and 2 warnings
|
python-unit (3.10)
Resource not accessible by integration - https://docs.github.com/rest/issues/comments#create-an-issue-comment
|
|
python-unit (3.10)
HttpError: Resource not accessible by integration - https://docs.github.com/rest/issues/comments#create-an-issue-comment
|
|
python-unit (3.10)
Permission denied when trying to create/update comment.
This PR is from a fork. GitHub restricts the GITHUB_TOKEN to read-only
for fork PRs triggered by the `pull_request` event.
To fix this, use the `pull_request_target` event instead:
```yaml
on:
pull_request_target:
types: [opened, synchronize, reopened]
permissions:
contents: read
pull-requests: write
```
Note: `pull_request_target` runs in the context of the base branch.
Be cautious when checking out fork code — never run untrusted code
from the fork with elevated permissions.
For more information, see:
https://github.com/MishaKav/pytest-coverage-comment#fork-prs
|
|
python-unit (3.14)
The strategy configuration was canceled because "python-unit._3_10" failed
|
|
python-unit (3.14)
Resource not accessible by integration - https://docs.github.com/rest/issues/comments#create-an-issue-comment
|
|
python-unit (3.14)
HttpError: Resource not accessible by integration - https://docs.github.com/rest/issues/comments#create-an-issue-comment
|
|
python-unit (3.14)
Permission denied when trying to create/update comment.
This PR is from a fork. GitHub restricts the GITHUB_TOKEN to read-only
for fork PRs triggered by the `pull_request` event.
To fix this, use the `pull_request_target` event instead:
```yaml
on:
pull_request_target:
types: [opened, synchronize, reopened]
permissions:
contents: read
pull-requests: write
```
Note: `pull_request_target` runs in the context of the base branch.
Be cautious when checking out fork code — never run untrusted code
from the fork with elevated permissions.
For more information, see:
https://github.com/MishaKav/pytest-coverage-comment#fork-prs
|
|
python-unit (3.13)
The strategy configuration was canceled because "python-unit._3_10" failed
|
|
python-unit (3.13)
The operation was canceled.
|
|
python-unit (3.11)
The strategy configuration was canceled because "python-unit._3_10" failed
|
|
python-unit (3.11)
The operation was canceled.
|
|
python-unit (3.12)
The strategy configuration was canceled because "python-unit._3_10" failed
|
|
python-unit (3.12)
The operation was canceled.
|
|
python-unit (3.10)
Your comment is too long (maximum is 65536 characters), coverage report will not be added.
Try one/some of the following options:
- Add "--cov-report=term-missing:skip-covered" to pytest command
- Add "hide-report: true" to hide detailed coverage table
- Add "report-only-changed-files: true" to show only changed files
- Add "xml-skip-covered: true" to hide files with 100% coverage
- Switch to "multiple-files" mode
- Add "remove-links-to-files: true" to remove file links
- Add "remove-links-to-lines: true" to remove line number links
|
|
python-unit (3.14)
Your comment is too long (maximum is 65536 characters), coverage report will not be added.
Try one/some of the following options:
- Add "--cov-report=term-missing:skip-covered" to pytest command
- Add "hide-report: true" to hide detailed coverage table
- Add "report-only-changed-files: true" to show only changed files
- Add "xml-skip-covered: true" to hide files with 100% coverage
- Switch to "multiple-files" mode
- Add "remove-links-to-files: true" to remove file links
- Add "remove-links-to-lines: true" to remove line number links
|