Skip to content

Benchmarks

Benchmarks #3160

Triggered via schedule May 1, 2026 04:20
Status Failure
Total duration 1h 13m 9s
Artifacts 12

benchmark.yml

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

Annotations

10 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."
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:09326cc97b79f195cd92991b66eda5c107881bb6548406b9320c52bdb5647824
benchmark-results-misc-CUDA
1.35 KB
sha256:6c2dd32d6036b131d1ba347a09c3735fc83b7acaeecdb9cc3f1eaf0c156c9ed4
benchmark-results-misc-TPU
1.35 KB
sha256:b5f0e28b9b27a8b9e4d130a91f6f0e76da5fa8c1ced6a01bec553ce361729760
benchmark-results-nn-CPU
1001 Bytes
sha256:8b4355fc47979faa60f3718e976fce21ebb3a83de276a5632b02665240bdee19
benchmark-results-nn-CUDA
1.69 KB
sha256:2952d5fb430437a3c962dcadfdf353a10f5afbc9d3ba30a60a12d370613ac7a4
benchmark-results-nn-TPU
1.65 KB
sha256:3942c093912628a137d092460fbd770b073b386b32be422b2ff74d0cc8995fbf
benchmark-results-oceananigans-CPU
555 Bytes
sha256:24103678acd5a5022735c571528dc7d900f3b2f00f4c1328571d852cd3228d1e
benchmark-results-oceananigans-CUDA
575 Bytes
sha256:a41d9beb8a501aa673d450df1abae9708731c49ca3909c6c815605cca9d87fd5
benchmark-results-oceananigans-TPU
567 Bytes
sha256:beb4423dd1b909d19279470f76deccfc8743505a405dac4de292f3686895a3ad
benchmark-results-polybench-CPU
1.52 KB
sha256:6a1ce10acfb862880771fcc8cc0fbfc5a26575c0332d185f89a1909a681c6804
benchmark-results-polybench-CUDA
1.59 KB
sha256:8abd4115619a1cee2efba4631d073c9058fa6a80cebb984ebb0393800c1c4c14
benchmark-results-polybench-TPU
1.58 KB
sha256:ef237b9b9ff72735b04f984fad8f67ddad0df4660bab80c8118bb0c7706efebd