Skip to content

wasmtime: read config from env variable TOML #1723

wasmtime: read config from env variable TOML

wasmtime: read config from env variable TOML #1723

Triggered via pull request April 14, 2026 08:27
Status Success
Total duration 1h 15m 31s
Artifacts

benchmarks.yml

on: pull_request
Fit to window
Zoom out
Zoom in

Annotations

5 warnings
benchmark
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: benchmark-action/github-action-benchmark@v1.20.7. 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/
benchmark-mem
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: benchmark-action/github-action-benchmark@v1.20.7. 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/
benchmark-http
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: benchmark-action/github-action-benchmark@v1.20.4. 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/
benchmark-http
Could not find external JSON file for benchmark data at /home/runner/work/runwasi/runwasi/cache/latency_results.json. Using empty default: Error: ENOENT: no such file or directory, open '/home/runner/work/runwasi/runwasi/cache/latency_results.json'
benchmark-stress
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: benchmark-action/github-action-benchmark@v1.20.7. 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/