Skip to content

Kernelguard pre-queue check addition #537

Kernelguard pre-queue check addition

Kernelguard pre-queue check addition #537

Triggered via pull request March 19, 2026 23:01
Status Failure
Total duration 56s
Artifacts 2

testing.yml

on: pull_request
unit-tests
54s
unit-tests
integration-tests-modal
13s
integration-tests-modal
integration-tests-github
11s
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-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/
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/
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/473/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/473/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/473 "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
148 KB
sha256:b418a4deebd47f6c5cdc39aee1376e4a99fe9ba2960c79f221c103c78725b934
python-coverage-comment-action
2.26 KB
sha256:802647a12ac701050ea2d5ed95419512f60a9ec70eff266236406e9b5a96982f