Skip to content

chore: make test and fixture names more explicit about no expiry #4403

chore: make test and fixture names more explicit about no expiry

chore: make test and fixture names more explicit about no expiry #4403

Triggered via push March 29, 2024 19:25
Status Success
Total duration 55s
Artifacts 1

tests-pytest.yml

on: push
Fit to window
Zoom out
Zoom in

Annotations

10 notices
pytest
Starting action
pytest
HTTP Request: GET https://api.github.com/repos/cal-itp/benefits "HTTP/1.1 200 OK"
pytest
Generating comment for PR
pytest
HTTP Request: GET https://api.github.com/repos/cal-itp/benefits/contents/data.json?ref=python-coverage-comment-action-data "HTTP/1.1 200 OK"
pytest
HTTP Request: GET https://api.github.com/repos/cal-itp/benefits/pulls?state=open&head=cal-itp%3Afeat%2Fexpiry-date&sort=updated&direction=desc "HTTP/1.1 200 OK"
pytest
HTTP Request: GET https://api.github.com/user "HTTP/1.1 403 Forbidden"
pytest
HTTP Request: GET https://api.github.com/repos/cal-itp/benefits/issues/1989/comments "HTTP/1.1 200 OK"
pytest
Update previous comment
pytest
HTTP Request: PATCH https://api.github.com/repos/cal-itp/benefits/issues/comments/2023987222 "HTTP/1.1 200 OK"
pytest
Ending action

Artifacts

Produced during runtime
Name Size
coverage-report Expired
160 KB