Skip to content

Update hf export data timings #528

Update hf export data timings

Update hf export data timings #528

Triggered via pull request March 16, 2026 22:52
Status Failure
Total duration 1m 4s
Artifacts 2

testing.yml

on: pull_request
unit-tests
1m 0s
unit-tests
integration-tests-modal
11s
integration-tests-modal
integration-tests-github
13s
integration-tests-github
Fit to window
Zoom out
Zoom in

Annotations

1 error, 3 warnings, and 10 notices
integration-tests-modal
Process completed with exit code 1.
integration-tests-modal
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, astral-sh/setup-uv@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
integration-tests-github
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, astral-sh/setup-uv@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
unit-tests
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/upload-artifact@v4, astral-sh/setup-uv@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
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/kernelbot/issues/469/comments "HTTP/1.1 403 Forbidden"
unit-tests
Adding new comment
unit-tests
HTTP Request: GET https://api.github.com/repos/gpu-mode/kernelbot/issues/469/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/kernelbot/contents/data.json?ref=python-coverage-comment-action-data "HTTP/1.1 200 OK"
unit-tests
HTTP Request: GET https://api.github.com/repos/gpu-mode/kernelbot/pulls/469 "HTTP/1.1 200 OK"
unit-tests
Generating comment for PR
unit-tests
HTTP Request: GET https://api.github.com/repos/gpu-mode/kernelbot "HTTP/1.1 200 OK"
unit-tests
Starting action

Artifacts

Produced during runtime
Name Size Digest
coverage Expired
135 KB
sha256:08a4e71f021eeb5f65d1f467fa136d5f3078899f6c4858346a421effa3466c33
python-coverage-comment-action Expired
1.13 KB
sha256:6a22082dbf1acfaa7a17ce166ccf38f81d6181d7086dc0c17f36092589342617