GV

GeezerVison

The World Wide Web, restored to 800 pixels of glory.

Home|About|Gaming cabinet|Archives|How it works|Starter sites

On this site

  • Sign in
  • ActionsCI/CD and automation
  • CodespacesCloud development environments
  • All Features
  • Documentation
  • Training
  • Certifications
  • Build with Copilot
  • Customize Copilot
  • Integrations
  • Trending repos
  • GitHub Sponsors
  • Developer articles
  • Enterprises

This view

  • Original page
  • New address

GeezerVison is showing github.com — chore: bump pinned valgrind-codspeed to 3.26.0-0codspeed10 by adriencaccia · Pull Request #593 · CodSpeedHQ/codspeed

Conversation

@adriencaccia

@adriencaccia adriencaccia commented Oct 22, 2026

Copy link
Copy Markdown
Member

Points the runner at valgrind-codspeed 3.26.0-0codspeed10, which keeps the guest's initial stack pointer fixed whatever the size of the arguments and environment (CodSpeedHQ/valgrind-codspeed#53), so simulated cache misses no longer vary with them.

The 6 hashes match the release's asset digests.

Refs COD-3971, which stays open for the runner v5.6.0 release this unblocks.

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.
greptile-apps[bot] reacted with thumbs up emoji
All reactions
  • 👍 1 reaction
@adriencaccia @claude
chore: bump pinned valgrind-codspeed to 3.26.0-0codspeed10
32caf34 
The new package keeps the guest's initial stack pointer fixed whatever
the size of the arguments and environment, so simulated cache misses no
longer vary with them.

Refs COD-3971
Co-Authored-By: Claude Opus 5.5 <[email protected]>
@codspeed

codspeed Bot commented Oct 22, 2026

Copy link
Copy Markdown

Merging this PR will not alter performance

2 warnings

⚠️ Walltime results may be unreliable

Some benchmarks used the Walltime instrument outside CodSpeed Macro Runners, which can make the results inconsistent.

Learn more about Macro Runners

See affected benchmarks

⚠️ 9 benchmarks are dominated by system calls

System calls cannot be simulated consistently and are left out of the measure. The reported value understates the real cost. Switch to the Walltime instrument to measure them.

Learn more about system calls

See affected benchmarks

🎉 Hooray! codspeed-rust just leveled up to 6.0.0!

A heads-up, this is a breaking change and it might affect your current performance baseline a bit. But here's the exciting part - it's packed with new, cool features and promises improved result stability 🥳!
Curious about what's new? Visit our releases page to delve into all the awesome details about this new version.

✅ 41 untouched benchmarks
⏩ 6 skipped benchmarks1

Comparing cod-3971-release-valgrind-codspeed-and-runner (32caf34) with main (53c7660)

Open in CodSpeed

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. ↩
All reactions

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.
@adriencaccia
adriencaccia marked this pull request as ready for review October 22, 2026 10:31
@adriencaccia
adriencaccia merged commit d13b184 into main Oct 22, 2026
66 checks passed

Uh oh!

There was an error while loading. Please reload this page.
@adriencaccia
adriencaccia deleted the cod-3971-release-valgrind-codspeed-and-runner branch October 22, 2026 10:31
@greptile-apps

greptile-apps Bot commented Oct 22, 2026 •
edited
Loading

Uh oh!

There was an error while loading. Please reload this page.

Copy link
Copy Markdown

RetriggerView in GreptileConfidence Score: 5/5

[Medium impact] The PR appears safe to merge; no actionable issues were found.

Summary

Updates the pinned Valgrind build to 3.26.0-0codspeed10, which fixes variation in the initial stack pointer caused by argument and environment sizes.

  • Valgrind benchmark runs keep simulated cache misses steady as arguments and environment sizes change.

Reviews (1) · Last reviewed commit: "chore: bump pinned valgrind-codspeed to ..." · Reviewed by Greptile
All reactions

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Uh oh!

There was an error while loading. Please reload this page.

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

Uh oh!

There was an error while loading. Please reload this page.

1 participant

@adriencaccia
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
You are visitor 01402520 — GeezerVison does not store the pages you look up.
Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required.