Skip to content
UnitTests

Use uv.lock to stop heroku crashes #16

Sign in to view logs

Use uv.lock to stop heroku crashes

Use uv.lock to stop heroku crashes #16

Triggered via pull request August 9, 2025 01:27
@msaroufimmsaroufim
synchronize #324
runtime
Status Success
Total duration 32s
Artifacts 2

unit_tests.yml

on: pull_request
unit-tests
26s
unit-tests
Fit to window
Zoom out
Zoom in

Annotations

10 notices
unit-tests
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).
unit-tests
HTTP Request: POST https://api.github.com/repos/gpu-mode/discord-cluster-manager/issues/324/comments "HTTP/1.1 403 Forbidden"
unit-tests
Adding new comment
unit-tests
HTTP Request: GET https://api.github.com/repos/gpu-mode/discord-cluster-manager/issues/324/comments "HTTP/1.1 200 OK"
unit-tests
HTTP Request: GET https://api.github.com/user "HTTP/1.1 403 Forbidden"
unit-tests
HTTP Request: GET https://api.github.com/repos/gpu-mode/discord-cluster-manager/contents/data.json?ref=python-coverage-comment-action-data "HTTP/1.1 404 Not Found"
unit-tests
HTTP Request: GET https://api.github.com/repos/gpu-mode/discord-cluster-manager/pulls/324 "HTTP/1.1 200 OK"
unit-tests
Generating comment for PR
unit-tests
HTTP Request: GET https://api.github.com/repos/gpu-mode/discord-cluster-manager "HTTP/1.1 200 OK"
unit-tests
Starting action

Artifacts

Produced during runtime
Name Size Digest
coverage Expired
85.6 KB
sha256:200d63dfcb4509e19c20db4968790771912652b99666556f1ed1763b465dcdfd
python-coverage-comment-action Expired
471 Bytes
sha256:9d4e60cea5f548523a6b3a1237e0303e7f85e67c964d94fa395af2ada8a35f33