Skip to content
UnitTests

leaderboard submit should show active leaderboards #20

Sign in to view logs

leaderboard submit should show active leaderboards

leaderboard submit should show active leaderboards #20

Triggered via pull request August 9, 2025 03:56
@msaroufimmsaroufim
opened #325
msaroufim-patch-4
Status Success
Total duration 34s
Artifacts 2

unit_tests.yml

on: pull_request
unit-tests
30s
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/325/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/325/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/325 "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:9730793e6f3b6b66a9aeeac1db0991be9d58dfb4b0bd613b28e7fa2ab24efb3e
python-coverage-comment-action Expired
1.12 KB
sha256:1d9f7373a3a59cb4594baca15020228e101c297bf20e151445361f2dee17b0f9