Skip to content

MAINT - CI improvements (security and maintenance) #576

MAINT - CI improvements (security and maintenance)

MAINT - CI improvements (security and maintenance) #576

Triggered via pull request January 15, 2025 14:31
Status Success
Total duration 6m 20s
Artifacts 2

CI.yml

on: pull_request
Matrix: run-pytest
Check coverage
40s
Check coverage
profiling
33s
profiling
coverage-comment  /  Display code coverage
0s
coverage-comment / Display code coverage
Fit to window
Zoom out
Zoom in

Annotations

9 warnings and 10 notices
run-pytest (ubuntu-latest, 3.10)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
run-pytest (ubuntu-latest, 3.11)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
run-pytest (ubuntu-latest, 3.12)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
run-pytest (ubuntu-latest, 3.13)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
run-pytest (ubuntu-latest, 3.9, 6.1)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
run-pytest (ubuntu-latest, 3.12, dev)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
run-pytest (ubuntu-latest, 3.9)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
profiling
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
Check coverage
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
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/2077/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/2539311904 "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.3 KB
python-coverage-comment-action
459 Bytes