Skip to content
CodSpeed Benchmarks

feat: add the tracegrind tool #137

Sign in to view logs

feat: add the tracegrind tool

feat: add the tracegrind tool #137

Triggered via pull request February 7, 2026 17:32
@art049art049
synchronize #8
tracegrind-tool
Status Failure
Total duration 3m 54s
Artifacts –

codspeed.yml

on: pull_request
Matrix: benchmarks
Fit to window
Zoom out
Zoom in

Annotations

29 errors
benchmarks (stress-ng --cpu 4 --cpu-ops 10, local)
Process completed with exit code 22.
benchmarks (stress-ng --cpu 1 --cpu-ops 10, local)
The strategy configuration was canceled because "benchmarks.stress-ng_--cpu_4_--cpu_3" failed
benchmarks (stress-ng --cpu 1 --cpu-ops 10, local)
The operation was canceled.
benchmarks (testdata/take_strings-aarch64 varbinview_non_null, local)
The strategy configuration was canceled because "benchmarks.stress-ng_--cpu_4_--cpu_3" failed
benchmarks (testdata/take_strings-aarch64 varbinview_non_null, local)
The operation was canceled.
benchmarks (echo Hello, World!, local)
The strategy configuration was canceled because "benchmarks.stress-ng_--cpu_4_--cpu_3" failed
benchmarks (echo Hello, World!, local)
The operation was canceled.
benchmarks (python3 testdata/test.py, local)
The strategy configuration was canceled because "benchmarks.stress-ng_--cpu_4_--cpu_3" failed
benchmarks (python3 testdata/test.py, local)
The operation was canceled.
benchmarks (testdata/take_strings-aarch64 varbinview_non_null, 3.25.1)
The strategy configuration was canceled because "benchmarks.stress-ng_--cpu_4_--cpu_3" failed
benchmarks (testdata/take_strings-aarch64 varbinview_non_null, 3.25.1)
The operation was canceled.
benchmarks (python3 testdata/test.py, 3.25.1)
The strategy configuration was canceled because "benchmarks.stress-ng_--cpu_4_--cpu_3" failed
benchmarks (python3 testdata/test.py, 3.25.1)
The operation was canceled.
benchmarks (stress-ng --cpu 1 --cpu-ops 10, 3.26.0)
The strategy configuration was canceled because "benchmarks.stress-ng_--cpu_4_--cpu_3" failed
benchmarks (stress-ng --cpu 1 --cpu-ops 10, 3.26.0)
The operation was canceled.
benchmarks (stress-ng --cpu 4 --cpu-ops 10, 3.26.0)
The strategy configuration was canceled because "benchmarks.stress-ng_--cpu_4_--cpu_3" failed
benchmarks (stress-ng --cpu 4 --cpu-ops 10, 3.26.0)
The operation was canceled.
benchmarks (testdata/take_strings-aarch64 varbinview_non_null, 3.26.0)
The strategy configuration was canceled because "benchmarks.stress-ng_--cpu_4_--cpu_3" failed
benchmarks (testdata/take_strings-aarch64 varbinview_non_null, 3.26.0)
The operation was canceled.
benchmarks (echo Hello, World!, 3.26.0)
The strategy configuration was canceled because "benchmarks.stress-ng_--cpu_4_--cpu_3" failed
benchmarks (echo Hello, World!, 3.26.0)
The operation was canceled.
benchmarks (stress-ng --cpu 4 --cpu-ops 10, 3.25.1)
The strategy configuration was canceled because "benchmarks.stress-ng_--cpu_4_--cpu_3" failed
benchmarks (python3 testdata/test.py, 3.26.0)
The strategy configuration was canceled because "benchmarks.stress-ng_--cpu_4_--cpu_3" failed
benchmarks (stress-ng --cpu 4 --cpu-ops 10, 3.25.1)
The operation was canceled.
benchmarks (python3 testdata/test.py, 3.26.0)
The operation was canceled.
benchmarks (stress-ng --cpu 1 --cpu-ops 10, 3.25.1)
The strategy configuration was canceled because "benchmarks.stress-ng_--cpu_4_--cpu_3" failed
benchmarks (stress-ng --cpu 1 --cpu-ops 10, 3.25.1)
The operation was canceled.
benchmarks (echo Hello, World!, 3.25.1)
The strategy configuration was canceled because "benchmarks.stress-ng_--cpu_4_--cpu_3" failed
benchmarks (echo Hello, World!, 3.25.1)
The operation was canceled.