Skip to content

Inject unified Tunix and vLLM environment fingerprinting metadata #6118

Inject unified Tunix and vLLM environment fingerprinting metadata

Inject unified Tunix and vLLM environment fingerprinting metadata #6118

Triggered via pull request May 14, 2026 00:42
Status Failure
Total duration 23m 16s
Artifacts 1

build_and_test_tunix.yml

on: pull_request
Build tunix package  /  Build Tunix wheel
9s
Build tunix package / Build Tunix wheel
tunix_tpu_unit_tests  /  run_prod
6m 58s
tunix_tpu_unit_tests / run_prod
tunix_tpu_unit_tests  /  run_dev
22m 48s
tunix_tpu_unit_tests / run_dev
tunix_cpu_unit_tests  /  run
3m 21s
tunix_cpu_unit_tests / run
Notify failed build
5s
Notify failed build
Fit to window
Zoom out
Zoom in

Annotations

3 errors and 4 warnings
tunix_tpu_unit_tests / run_prod
Executing the custom container implementation failed. Please contact your self hosted runner administrator.
tunix_tpu_unit_tests / run_prod
Process completed with exit code 1.
tunix_tpu_unit_tests / run_prod
Error: ScriptExecutorError when trying to execute: "Error: Job failed with exit code 1."
Build tunix package / Build Tunix wheel
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683, actions/setup-python@v4, actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 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/
tunix_cpu_unit_tests / run
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/download-artifact@634f93cb2916e3fdff6788551b99b062d0335ce0, actions/setup-python@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 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/
tunix_tpu_unit_tests / run_prod
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 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/
tunix_tpu_unit_tests / run_dev
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 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/

Artifacts

Produced during runtime
Name Size Digest
tunix-wheel
444 KB
sha256:a860520fba19bcb4006f6b3ba84074406916940373f8fbbb2b54786e57b751b6