Skip to content

DEV - Add Fontawesome scripts to build assets #320

DEV - Add Fontawesome scripts to build assets

DEV - Add Fontawesome scripts to build assets #320

Triggered via pull request September 18, 2024 14:35
Status Failure
Total duration 11m 9s
Artifacts 3

CI.yml

on: pull_request
Matrix: build PST docs
Matrix: run-pytest
a11y-tests (ubuntu-latest, 3.12)
3m 44s
a11y-tests (ubuntu-latest, 3.12)
lighthouse-audit
4m 32s
lighthouse-audit
profiling
32s
profiling
Check coverage
54s
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/1982/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/2346841862 "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
16.2 KB
lighthouse-results
5.22 MB
python-coverage-comment-action
461 Bytes