PR Test

PR Test Base #223

Sign in to view logs

Triggered via schedule May 28, 2026 19:38

scottgl9

main

Status Cancelled

Total duration 1d 8h 17m 11s

Artifacts –

pr-test.yml

on: schedule

call-gate / pr-gate

Matrix: Build Wheel

wait-for-stage-a

Matrix: Build Wheel Arm

Matrix: stage-a-test-cpu

call-jit-kernel-tests / jit-kernel-b200-test

call-jit-kernel-tests / jit-kernel-benchmark-test

call-jit-kernel-tests / jit-kernel-multigpu-unit-test

call-jit-kernel-tests / jit-kernel-unit-test

call-multimodal-gen-tests / compute-diffusion-partitions

stage-a-test-1-gpu-small

call-multimodal-gen-tests / multimodal-gen-component-accuracy

call-multimodal-gen-tests / multimodal-gen-test-1-b200

call-multimodal-gen-tests / multimodal-gen-unit-test

call-sgl-kernel-tests / sgl-kernel-b200-test

call-sgl-kernel-tests / sgl-kernel-benchmark-test

call-sgl-kernel-tests / sgl-kernel-mla-test

call-sgl-kernel-tests / sgl-kernel-unit-test

wait-for-stage-b

Matrix: stage-b-test-1-gpu-large

Matrix: stage-b-test-1-gpu-small

Matrix: stage-b-test-2-gpu-large

stage-b-test-4-gpu-b200

Matrix: call-multimodal-gen-tests / multimodal-gen-test-1-gpu

Matrix: call-multimodal-gen-tests / multimodal-gen-test-2-gpu

Matrix: stage-c-test-4-gpu-b200

Matrix: stage-c-test-4-gpu-h100

Matrix: stage-c-test-8-gpu-h20

Matrix: stage-c-test-8-gpu-h200

stage-c-test-deepep-4-gpu-h100

stage-c-test-deepep-8-gpu-h200

call-multimodal-gen-tests / diffusion-coverage-check

Annotations

56 errors and 6 warnings

stage-b-test-1-gpu-small (2)

The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s

stage-b-test-2-gpu-large (3)

The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s

stage-c-test-8-gpu-h200 (1)

The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s

stage-b-test-1-gpu-large (11)

The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s

stage-a-test-1-gpu-small

The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s

stage-b-test-4-gpu-b200

The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s

stage-b-test-1-gpu-large (3)

The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s

stage-c-test-8-gpu-h200 (0)

The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s

stage-c-test-8-gpu-h20 (1)

The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s

stage-b-test-1-gpu-large (4)

The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s

call-multimodal-gen-tests / multimodal-gen-component-accuracy

The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s

stage-b-test-1-gpu-large (10)

The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s

call-multimodal-gen-tests / multimodal-gen-unit-test

The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s

stage-c-test-4-gpu-b200 (3)

The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s

stage-b-test-1-gpu-large (12)

The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s

stage-c-test-8-gpu-h200 (3)

The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s

stage-b-test-1-gpu-small (1)

The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s

stage-c-test-deepep-4-gpu-h100

The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s

stage-c-test-4-gpu-b200 (5)

The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s

stage-c-test-4-gpu-h100 (0)

The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s

stage-b-test-1-gpu-small (0)

The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s

stage-b-test-2-gpu-large (0)

The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s

stage-c-test-4-gpu-b200 (0)

The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s

stage-b-test-2-gpu-large (2)

The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s

stage-b-test-1-gpu-large (9)

The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s

stage-b-test-1-gpu-small (3)

The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s

stage-b-test-1-gpu-large (2)

The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s

stage-b-test-1-gpu-large (8)

The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s

stage-b-test-1-gpu-small (5)

The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s

stage-c-test-4-gpu-h100 (1)

The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s

stage-b-test-1-gpu-small (4)

The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s

stage-b-test-1-gpu-large (6)

The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s

stage-c-test-4-gpu-b200 (4)

The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s

stage-b-test-1-gpu-large (7)

The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s

stage-b-test-1-gpu-large (1)

The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s

stage-c-test-4-gpu-b200 (2)

The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s

stage-b-test-1-gpu-small (6)

The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s

stage-c-test-4-gpu-h100 (2)

The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s

stage-b-test-1-gpu-large (13)

The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s

stage-c-test-deepep-8-gpu-h200

The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s

stage-b-test-1-gpu-large (5)

The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s

stage-b-test-2-gpu-large (1)

The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s

stage-b-test-1-gpu-small (7)

The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s

stage-c-test-4-gpu-b200 (1)

The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s

stage-c-test-8-gpu-h200 (2)

The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s

stage-c-test-8-gpu-h20 (0)

The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s

stage-b-test-1-gpu-large (0)

The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s

call-multimodal-gen-tests / multimodal-gen-test-1-gpu (2)

The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s

call-multimodal-gen-tests / multimodal-gen-test-2-gpu (0)

The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s

call-multimodal-gen-tests / multimodal-gen-test-1-gpu (0)

The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s

call-multimodal-gen-tests / multimodal-gen-test-2-gpu (1)

The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s

call-multimodal-gen-tests / multimodal-gen-test-2-gpu (2)

The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s

call-multimodal-gen-tests / multimodal-gen-test-1-gpu (1)

The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s

pr-test-finish

Process completed with exit code 1.

Canceling since a higher priority waiting request for pr-test-schedule-main-current-all exists

Canceling since a higher priority waiting request for pr-test-schedule-main-current-all exists

check-changes

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 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/

call-multimodal-gen-tests / compute-diffusion-partitions

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/setup-python@v5. 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/

stage-a-test-cpu (2)

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/github-script@v7, actions/setup-python@v5, astral-sh/setup-uv@v5. 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/

stage-a-test-cpu (1)

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/github-script@v7, actions/setup-python@v5, astral-sh/setup-uv@v5. 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/

stage-a-test-cpu (3)

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/github-script@v7, actions/setup-python@v5, astral-sh/setup-uv@v5. 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/

stage-a-test-cpu (0)

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/github-script@v7, actions/setup-python@v5, astral-sh/setup-uv@v5. 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/