Skip to content

Fix nbsphinx color outputs, suppress other notebook output Axe errors #163

Fix nbsphinx color outputs, suppress other notebook output Axe errors

Fix nbsphinx color outputs, suppress other notebook output Axe errors #163

Triggered via pull request June 28, 2024 12:19
Status Success
Total duration 8m 4s
Artifacts 3

CI.yml

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

Annotations

1 error, 2 warnings, and 10 notices
a11y-tests (ubuntu-latest, 3.12)
Process completed with exit code 255.
check coverage
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/upload-artifact@v3. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
Deprecation notice: v1, v2, and v3 of the artifact actions
The following artifacts were uploaded using a version of actions/upload-artifact that is scheduled for deprecation: "python-coverage-comment-action". Please update your workflow to use v4 of the artifact actions. Learn more: https://github.blog/changelog/2024-04-16-deprecation-notice-v3-of-the-artifact-actions/
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/1905/comments "HTTP/1.1 200 OK"
check coverage
Adding new comment
check coverage
HTTP Request: POST https://api.github.com/repos/pydata/pydata-sphinx-theme/issues/1905/comments "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.17 MB
python-coverage-comment-action Expired
10.2 KB