Skip to content

Benchmarks

Benchmarks #3131

Triggered via schedule April 25, 2026 03:56
Status Failure
Total duration 1h 37m 23s
Artifacts 12

benchmark.yml

on: schedule
determine-suites
55s
determine-suites
Matrix: benchmark
benchmark-aggregate
0s
benchmark-aggregate
Notify failed build
3s
Notify failed build
Fit to window
Zoom out
Zoom in

Annotations

11 errors and 1 warning
benchmark (comrade, linux-x86-ct6e-180-4tpu)
Executing the custom container implementation failed. Please contact your self hosted runner administrator.
benchmark (comrade, linux-x86-ct6e-180-4tpu)
Process completed with exit code 1.
benchmark (comrade, linux-x86-ct6e-180-4tpu)
Error: ScriptExecutorError when trying to execute: "Error: Job failed with exit code 1."
benchmark (comrade, linux-x86-n2-32)
Executing the custom container implementation failed. Please contact your self hosted runner administrator.
benchmark (comrade, linux-x86-n2-32)
Process completed with exit code 1.
benchmark (comrade, linux-x86-n2-32)
Error: ScriptExecutorError when trying to execute: "Error: Job failed with exit code 1."
benchmark (comrade, linux-x86-a2-48-a100-4gpu)
Executing the custom container implementation failed. Please contact your self hosted runner administrator.
benchmark (comrade, linux-x86-a2-48-a100-4gpu)
Process completed with exit code 1.
benchmark (comrade, linux-x86-a2-48-a100-4gpu)
Error: ScriptExecutorError when trying to execute: "Error: Job failed with exit code 1."
benchmark (nn, linux-x86-n2-32)
The job has exceeded the maximum execution time of 1h30m0s
Notify failed build
Resource not accessible by integration
Notify failed build
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: jayqi/failed-build-issue-action@v1. 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
benchmark-results-misc-CPU
1.2 KB
sha256:0b71354743376e1d1fa0fd2c131ed28e73a9e2d279af5914affd99ef2b615064
benchmark-results-misc-CUDA
1.33 KB
sha256:7d2c1dfa136fa212223ee6e4c0299cc0eda4c10fabc0ef3a1cdce5e168720b19
benchmark-results-misc-TPU
1.34 KB
sha256:c798b5056d6172d00d93beaafb3b2afda94350fa6bccab6e9914de2c450b6ed6
benchmark-results-nn-CPU
1008 Bytes
sha256:0765e1aaf491276982884cfd2d7bf1a6c8be0032d4c32b4f78df5d30740dc816
benchmark-results-nn-CUDA
1.69 KB
sha256:4d4ff3e0ddac4cdec391536eec462c1e76ace01aea199c90af230e81fc1ade28
benchmark-results-nn-TPU
1.65 KB
sha256:0003c011d74edbdcbf226043f2695040e54559fd82791bfd5461c8e2af48491c
benchmark-results-oceananigans-CPU
555 Bytes
sha256:ea4b464884bd79632b7414eb5743fbd7c4f98926df3f22e38d1467427241b441
benchmark-results-oceananigans-CUDA
574 Bytes
sha256:02e0f7bdd61a1641522516a7537446e8c6481702cbdb9987c2f7a343968301e2
benchmark-results-oceananigans-TPU
567 Bytes
sha256:5eed1cd74e8e9ff1761dcf3122e798e8bc21b5562d030f2453dc708402f20854
benchmark-results-polybench-CPU
1.51 KB
sha256:1cbe74642042141976012e34eda8f3bb67617734970274e5a4d3392e6d335bfb
benchmark-results-polybench-CUDA
1.58 KB
sha256:f4c2aa5f9859b7d2578248b19db365c7b8b99f40a29274d2f7b013cd903f566f
benchmark-results-polybench-TPU
1.58 KB
sha256:93818bb036a4359dc7f1fddfbe62a48a092106ad6ca083135c757a63ae5d1f3b