Skip to content

Nightly Release

Nightly Release #131

Triggered via schedule April 17, 2026 02:06
Status Cancelled
Total duration 1d 0h 0m 16s
Artifacts 2

nightly-release.yml

on: schedule
Matrix: build-flashinfer-jit-cache
build-flashinfer-python
32s
build-flashinfer-python
build-flashinfer-cubin
4m 19s
build-flashinfer-cubin
Matrix: test-nightly-build
create-release
0s
create-release
jit-cache-summary
5s
jit-cache-summary
update-wheel-index
0s
update-wheel-index
Fit to window
Zoom out
Zoom in

Annotations

6 errors and 4 warnings
build-flashinfer-jit-cache (12.8, x86_64)
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
build-flashinfer-jit-cache (13.0, aarch64)
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
build-flashinfer-jit-cache (12.9, x86_64)
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
build-flashinfer-jit-cache (13.0, x86_64)
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
build-flashinfer-jit-cache (12.8, aarch64)
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
build-flashinfer-jit-cache (12.9, aarch64)
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
setup
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/
build-flashinfer-python
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/upload-artifact@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/
build-flashinfer-cubin
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/upload-artifact@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/
jit-cache-summary
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@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/

Artifacts

Produced during runtime
Name Size Digest
flashinfer-cubin-wheel Expired
99.7 MB
sha256:1f04e33abc8520ccf86442b8d5ab9ef741f9a50ca96c0d86500357625450eed2
flashinfer-python-dist Expired
11.4 MB
sha256:c41fe1e2cff8ea12950475c401a4b876539d773f39956759201a867ed5df1123