Skip to content

TritonBench

TritonBench #535

Triggered via schedule July 13, 2026 12:44
Status Failure
Total duration 3h 22m 19s
Artifacts 1

tritonbench.yml

on: schedule
set-parameters
7s
set-parameters
Matrix: Run TritonBench benchmarks
Fit to window
Zoom out
Zoom in

Annotations

3 errors and 1 warning
Run TritonBench benchmarks (linux.dgx.b200, meta-triton, tlx)
The self-hosted runner lost communication with the server. Verify the machine is running and has a healthy network connection. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.
Run TritonBench benchmarks (linux.dgx.b200, meta-triton, nightly)
The self-hosted runner lost communication with the server. Verify the machine is running and has a healthy network connection. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.
Run TritonBench benchmarks (linux.dgx.b200, triton-main, nightly)
The self-hosted runner lost communication with the server. Verify the machine is running and has a healthy network connection. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.
set-parameters
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/checkout@v4, actions/setup-python@v5. 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
tritonbench-linux.dgx.b200-benchmark-meta-triton-periodic-tlx Expired
1.38 KB
sha256:d94f8f7630a9cf43753a873778e333ba901fbe2aef8c59726057d75caabaa33b