Skip to content

BUG - Remove schedule trigger for comment action #183

BUG - Remove schedule trigger for comment action

BUG - Remove schedule trigger for comment action #183

Triggered via pull request July 3, 2024 19:58
Status Failure
Total duration 8m 34s
Artifacts 3

CI.yml

on: pull_request
Matrix: build PST docs
Matrix: run-pytest
a11y-tests (ubuntu-latest, 3.12)
3m 39s
a11y-tests (ubuntu-latest, 3.12)
lighthouse-audit
4m 6s
lighthouse-audit
profiling
17s
profiling
check coverage
24s
check coverage
Fit to window
Zoom out
Zoom in

Annotations

1 error and 10 notices
a11y-tests (ubuntu-latest, 3.12)
Process completed with exit code 255.
check coverage
Starting action
check coverage
HTTP Request: GET https://api.github.com/repos/pydata/pydata-sphinx-theme "HTTP/1.1 200 OK"
check coverage
Generating comment for PR
check coverage
HTTP Request: GET https://api.github.com/repos/pydata/pydata-sphinx-theme/contents/data.json?ref=python-coverage-comment-action-data "HTTP/1.1 200 OK"
check coverage
HTTP Request: GET https://api.github.com/user "HTTP/1.1 403 Forbidden"
check coverage
HTTP Request: GET https://api.github.com/repos/pydata/pydata-sphinx-theme/issues/1914/comments "HTTP/1.1 200 OK"
check coverage
Update previous comment
check coverage
HTTP Request: PATCH https://api.github.com/repos/pydata/pydata-sphinx-theme/issues/comments/2199877866 "HTTP/1.1 403 Forbidden"
check coverage
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).
check coverage
Ending action

Artifacts

Produced during runtime
Name Size
coverage-data-3.12 Expired
16.2 KB
lighthouse-results Expired
5.21 MB
python-coverage-comment-action Expired
1.79 KB