Skip to content
CodSpeed

feat: collect Python toolchain information via instrument hooks environment API #662

Sign in to view logs

feat: collect Python toolchain information via instrument hooks environment API

feat: collect Python toolchain information via instrument hooks environment API #662

Triggered via pull request April 2, 2026 08:03
@GuillaumeLagrangeGuillaumeLagrange
synchronize #108
cod-2416-implement-toolchain-harvesting-for-node-python-and-go
Status Success
Total duration 7m 3s
Artifacts –

codspeed.yml

on: pull_request
Matrix: benchmarks
all-checks
3s
all-checks
Fit to window
Zoom out
Zoom in

Annotations

52 warnings
Run memory benchmarks (Shard #1)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0057852bfaa89a56745cba8c7296529d2fc39830, actions/github-script@f28e40c7f34bde8b3046d885e986cb6290c5673b. 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/
Run memory benchmarks (Shard #4)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0057852bfaa89a56745cba8c7296529d2fc39830, actions/github-script@f28e40c7f34bde8b3046d885e986cb6290c5673b. 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/
Run memory benchmarks (Shard #3)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0057852bfaa89a56745cba8c7296529d2fc39830, actions/github-script@f28e40c7f34bde8b3046d885e986cb6290c5673b. 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/
Run memory benchmarks (Shard #2)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0057852bfaa89a56745cba8c7296529d2fc39830, actions/github-script@f28e40c7f34bde8b3046d885e986cb6290c5673b. 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/
Run simulation benchmarks (Shard #4)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0057852bfaa89a56745cba8c7296529d2fc39830, actions/github-script@f28e40c7f34bde8b3046d885e986cb6290c5673b. 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/
Run simulation benchmarks (Shard #3)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0057852bfaa89a56745cba8c7296529d2fc39830, actions/github-script@f28e40c7f34bde8b3046d885e986cb6290c5673b. 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/
Run simulation benchmarks (Shard #1)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0057852bfaa89a56745cba8c7296529d2fc39830, actions/github-script@f28e40c7f34bde8b3046d885e986cb6290c5673b. 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/
Run simulation benchmarks (Shard #2)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0057852bfaa89a56745cba8c7296529d2fc39830, actions/github-script@f28e40c7f34bde8b3046d885e986cb6290c5673b. 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/
Run walltime benchmarks (Shard #4)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0057852bfaa89a56745cba8c7296529d2fc39830, actions/github-script@f28e40c7f34bde8b3046d885e986cb6290c5673b. 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/
Run walltime benchmarks (Shard #4)
Failed to convert jit dump into perf map: Failed to read from the jitdump file: unexpected end of file Caused by: unexpected end of file
Run walltime benchmarks (Shard #4)
Failed to convert jit dump into perf map: Failed to read from the jitdump file: unexpected end of file Caused by: unexpected end of file
Run walltime benchmarks (Shard #4)
Failed to convert jit dump into perf map: Failed to read from the jitdump file: unexpected end of file Caused by: unexpected end of file
Run walltime benchmarks (Shard #4)
Failed to convert jit dump into perf map: Failed to read from the jitdump file: unexpected end of file Caused by: unexpected end of file
Run walltime benchmarks (Shard #4)
Failed to convert jit dump into perf map: Failed to read from the jitdump file: unexpected end of file Caused by: unexpected end of file
Run walltime benchmarks (Shard #4)
Failed to convert jit dump into perf map: Failed to read from the jitdump file: unexpected end of file Caused by: unexpected end of file
Run walltime benchmarks (Shard #4)
Failed to convert jit dump into perf map: Failed to read from the jitdump file: unexpected end of file Caused by: unexpected end of file
Run walltime benchmarks (Shard #4)
Failed to convert jit dump into perf map: Failed to read from the jitdump file: unexpected end of file Caused by: unexpected end of file
Run walltime benchmarks (Shard #4)
Failed to convert jit dump into perf map: Failed to read from the jitdump file: unexpected end of file Caused by: unexpected end of file
Run walltime benchmarks (Shard #4)
Failed to convert jit dump into perf map: Failed to read from the jitdump file: unexpected end of file Caused by: unexpected end of file
Run walltime benchmarks (Shard #1)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0057852bfaa89a56745cba8c7296529d2fc39830, actions/github-script@f28e40c7f34bde8b3046d885e986cb6290c5673b. 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/
Run walltime benchmarks (Shard #1)
Failed to convert jit dump into perf map: Failed to read from the jitdump file: unexpected end of file Caused by: unexpected end of file
Run walltime benchmarks (Shard #1)
Failed to convert jit dump into perf map: Failed to read from the jitdump file: unexpected end of file Caused by: unexpected end of file
Run walltime benchmarks (Shard #1)
Failed to convert jit dump into perf map: Failed to read from the jitdump file: unexpected end of file Caused by: unexpected end of file
Run walltime benchmarks (Shard #1)
Failed to convert jit dump into perf map: Failed to read from the jitdump file: unexpected end of file Caused by: unexpected end of file
Run walltime benchmarks (Shard #1)
Failed to convert jit dump into perf map: Failed to read from the jitdump file: unexpected end of file Caused by: unexpected end of file
Run walltime benchmarks (Shard #1)
Failed to convert jit dump into perf map: Failed to read from the jitdump file: unexpected end of file Caused by: unexpected end of file
Run walltime benchmarks (Shard #1)
Failed to convert jit dump into perf map: Failed to read from the jitdump file: unexpected end of file Caused by: unexpected end of file
Run walltime benchmarks (Shard #1)
Failed to convert jit dump into perf map: Failed to read from the jitdump file: unexpected end of file Caused by: unexpected end of file
Run walltime benchmarks (Shard #1)
Failed to convert jit dump into perf map: Failed to read from the jitdump file: unexpected end of file Caused by: unexpected end of file
Run walltime benchmarks (Shard #1)
Failed to convert jit dump into perf map: Failed to read from the jitdump file: unexpected end of file Caused by: unexpected end of file
Run walltime benchmarks (Shard #3)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0057852bfaa89a56745cba8c7296529d2fc39830, actions/github-script@f28e40c7f34bde8b3046d885e986cb6290c5673b. 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/
Run walltime benchmarks (Shard #3)
Failed to convert jit dump into perf map: Failed to read from the jitdump file: unexpected end of file Caused by: unexpected end of file
Run walltime benchmarks (Shard #3)
Failed to convert jit dump into perf map: Failed to read from the jitdump file: unexpected end of file Caused by: unexpected end of file
Run walltime benchmarks (Shard #3)
Failed to convert jit dump into perf map: Failed to read from the jitdump file: unexpected end of file Caused by: unexpected end of file
Run walltime benchmarks (Shard #3)
Failed to convert jit dump into perf map: Failed to read from the jitdump file: unexpected end of file Caused by: unexpected end of file
Run walltime benchmarks (Shard #3)
Failed to convert jit dump into perf map: Failed to read from the jitdump file: unexpected end of file Caused by: unexpected end of file
Run walltime benchmarks (Shard #3)
Failed to convert jit dump into perf map: Failed to read from the jitdump file: unexpected end of file Caused by: unexpected end of file
Run walltime benchmarks (Shard #3)
Failed to convert jit dump into perf map: Failed to read from the jitdump file: unexpected end of file Caused by: unexpected end of file
Run walltime benchmarks (Shard #3)
Failed to convert jit dump into perf map: Failed to read from the jitdump file: unexpected end of file Caused by: unexpected end of file
Run walltime benchmarks (Shard #3)
Failed to convert jit dump into perf map: Failed to read from the jitdump file: unexpected end of file Caused by: unexpected end of file
Run walltime benchmarks (Shard #3)
Failed to convert jit dump into perf map: Failed to read from the jitdump file: unexpected end of file Caused by: unexpected end of file
Run walltime benchmarks (Shard #2)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0057852bfaa89a56745cba8c7296529d2fc39830, actions/github-script@f28e40c7f34bde8b3046d885e986cb6290c5673b. 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/
Run walltime benchmarks (Shard #2)
Failed to convert jit dump into perf map: Failed to read from the jitdump file: unexpected end of file Caused by: unexpected end of file
Run walltime benchmarks (Shard #2)
Failed to convert jit dump into perf map: Failed to read from the jitdump file: unexpected end of file Caused by: unexpected end of file
Run walltime benchmarks (Shard #2)
Failed to convert jit dump into perf map: Failed to read from the jitdump file: unexpected end of file Caused by: unexpected end of file
Run walltime benchmarks (Shard #2)
Failed to convert jit dump into perf map: Failed to read from the jitdump file: unexpected end of file Caused by: unexpected end of file
Run walltime benchmarks (Shard #2)
Failed to convert jit dump into perf map: Failed to read from the jitdump file: unexpected end of file Caused by: unexpected end of file
Run walltime benchmarks (Shard #2)
Failed to convert jit dump into perf map: Failed to read from the jitdump file: unexpected end of file Caused by: unexpected end of file
Run walltime benchmarks (Shard #2)
Failed to convert jit dump into perf map: Failed to read from the jitdump file: unexpected end of file Caused by: unexpected end of file
Run walltime benchmarks (Shard #2)
Failed to convert jit dump into perf map: Failed to read from the jitdump file: unexpected end of file Caused by: unexpected end of file
Run walltime benchmarks (Shard #2)
Failed to convert jit dump into perf map: Failed to read from the jitdump file: unexpected end of file Caused by: unexpected end of file
Run walltime benchmarks (Shard #2)
Failed to convert jit dump into perf map: Failed to read from the jitdump file: unexpected end of file Caused by: unexpected end of file