[dependabot]

Bumps CodSpeedHQ/action from 5.0.2 to 5.4.0.

Release notes

Sourced from CodSpeedHQ/action's releases.

v5.4.0

Bumps the CodSpeed runner to v5.4.0, including v5.3.0 and v5.3.1.

The Memory instrument now tracks physical (resident) memory and captures allocation call stacks to build memory flamegraphs. Both are enabled by default and can be turned off with the new disable-memory-track-physical and disable-memory-capture-stack inputs. Serialization is also faster on large memory benchmarks.

The action now exposes the id of the CodSpeed run as a run-id output, and CodSpeed now works on non-Ubuntu/Debian distributions such as Arch Linux.

🚀 Features

• Track physical memory and capture allocation call stacks for memory flamegraphs, both enabled by default by @​not-matthias in #529, #522 and #553
• Expose the run id as a GitHub Actions step output by @​moha-bekh in #551
• Add an --experimental-disable-pythonmalloc-override flag (CODSPEED_EXPERIMENTAL_DISABLE_PYTHONMALLOC_OVERRIDE) to stop overriding the Python allocator, which can break free-threaded Python in simulation mode, by @​not-matthias in #539
• Apply kernel memory tunables before memory-mode runs, and fail early when the kernel has no BTF by @​not-matthias in #507 and #524
• Pause producers under ring buffer pressure in memory mode, and log process stops per reason by @​not-matthias in #543
• Log which authentication method the run uses by @​fargito in #521

🐛 Bug Fixes

• Support distributions CodSpeed publishes no valgrind package for (Arch, rolling releases) by @​moha-bekh in #525
• Error out when the profile archive exceeds the upload size limit by @​lvaroqui in #557
• Detect free-threaded Python from venv and uv before setting PYTHONMALLOC by @​not-matthias in #539
• Honor deprecated experimental flags, including their falsey values, instead of ignoring them by @​not-matthias in #532 and #553
• Fix memory tracking edge cases: reused pids, stack-ring overflow, BPF links held by forked processes, and allocator symbols aliased at an attached offset by @​not-matthias in #522 and #543
• Attach memory tracking hooks without perf_event_open by @​GuillaumeLagrange in #536
• Restore profiling sysctls in walltime mode by @​not-matthias in #507

⚡ Performance

• Speed up memory serialization and reduce the tracker's memory usage on large memory benchmarks by @​not-matthias in #522, #537, #548, #558 and #560

⚙️ Internals

• Pin memtrack to 1.6.0, through 1.5.0 and 1.5.1, by @​adriencaccia in #530, #541 and #561
• Keep mmap/munmap/brk as deprecated memtrack artifact variants by @​GuillaumeLagrange in #538

Full Runner Changelog: https://github.com/CodSpeedHQ/codspeed/blob/main/CHANGELOG.md

What's Changed

• chore: bump runner version to 5.3.0 by @​github-actions[bot] in CodSpeedHQ/action#239
• feat: add memory-track-physical experimental input by @​not-matthias in CodSpeedHQ/action#238
• chore: bump runner version to 5.3.1 by @​github-actions[bot] in CodSpeedHQ/action#240
• feat: add a run-id output by @​moha-bekh in CodSpeedHQ/action#243
• chore: bump runner version to 5.4.0 by @​github-actions[bot] in CodSpeedHQ/action#244
• feat: add disable-memory-capture-stack and disable-memory-track-physical inputs by @​not-matthias in CodSpeedHQ/action#242

New Contributors

• @​moha-bekh made their first contribution in CodSpeedHQ/action#243

... (truncated)

Commits

• c4fd08a Release v5.4.0 🚀
• 759ae97 feat: add disable-memory-capture-stack and disable-memory-track-physical inputs
• fe42bc0 chore: bump runner version to 5.4.0 (#244)
• c205870 feat: add a run-id output (#243)
• 48820ec chore: bump runner version to 5.3.1 (#240)
• 0fc899a feat: add experimental-memory-track-physical input
• 2d26491 chore: bump runner version to 5.3.0 (#239)
• 373d686 Release v5.2.1 🚀
• 5659c65 chore: bump runner version to 5.2.1 (#236)
• 22d40ad feat: add simulation-track-subprocess input (#235)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[codspeed]

Merging this PR will not alter performance

ℹ️ 12 benchmarks have no flame graph

The flamegraph could not be generated because we failed to resolve the symbols in the profiling trace. This happens when we fail to harvest information about language frames.

• test_config_create_full
• test_config_create_minimal
• test_cache_config_creation
• test_json_roundtrip
• test_json_serialize_large
• test_content_delta_from_json
• test_llm_result_simple
• test_llm_result_with_tool_calls
• test_sse_event_content_delta
• test_sse_event_task_completed
• …and 2 more

✅ 34 untouched benchmarks
⏩ 6 skipped benchmarks¹

---

_{Comparing dependabot/github_actions/develop/CodSpeedHQ/action-5.4.0 (dc8f4e0) with develop (aa60dc5)}

Footnotes

1. 6 benchmarks were skipped, so the baseline results were used instead. If they were deleted from the codebase, click here and archive them to remove them from the performance reports. ↩