Skip to content

fix: avoid using the same route as the one for legitimate server errors #7698

fix: avoid using the same route as the one for legitimate server errors

fix: avoid using the same route as the one for legitimate server errors #7698

Triggered via push February 25, 2025 21:56
Status Success
Total duration 1m 15s
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%3Afix%2Ftest-error-url&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/2702/comments "HTTP/1.1 200 OK"
pytest
Update previous comment
pytest
HTTP Request: PATCH https://api.github.com/repos/cal-itp/benefits/issues/comments/2683300124 "HTTP/1.1 200 OK"
pytest
Ending action

Artifacts

Produced during runtime
Name Size
coverage-report
254 KB