Skip to content

Unique Playwright trace names to avoid collisions #765

Unique Playwright trace names to avoid collisions

Unique Playwright trace names to avoid collisions #765

Triggered via pull request March 11, 2025 18:21
Status Success
Total duration 7m 43s
Artifacts 1

CI.yml

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

Annotations

1 warning and 9 notices
run-pytest (macos-14, 3.13)
These files were overwritten during the `brew link` step:
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/2161/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/2711856476 "HTTP/1.1 200 OK"
Check coverage
Ending action

Artifacts

Produced during runtime
Name Size
coverage-data-3.12
16.4 KB