Update benchmark to v1.9.3

[laurynas-biveinis]

Summary by CodeRabbit

• Chores
  • Updated third-party benchmark library to a newer version.

[coderabbitai]

Walkthrough

The commit reference for the 3rd_party/benchmark subproject was updated to a newer version. No other files or code were changed.

Changes

File(s)	Change Summary
3rd_party/benchmark	Updated subproject commit reference to a newer commit.

Possibly related PRs

• Update benchmark to v1.9.2 #774: Updates the same 3rd_party/benchmark subproject to a newer commit.
• Update benchmark to v1.9.1 #608: Also updates the commit reference for 3rd_party/benchmark.

Poem

Another commit hash, another day,
Benchmark moves along its way.
Old code replaced with something new,
Just a pointer changed—nothing else to do.
Progress in silence, swift and neat,
The update’s done, the circle’s complete.

Tip

⚡️ Faster reviews with caching

• CodeRabbit now supports caching for code and dependencies, helping speed up reviews. This means quicker feedback, reduced wait times, and a smoother review experience overall. Cached data is encrypted and stored securely. This feature will be automatically enabled for all accounts on May 16th. To opt out, configure Review - Disable Cache at either the organization or repository level. If you prefer to disable all data retention across your organization, simply turn off the Data Retention setting under your Organization Settings.

Enjoy the performance boost—your workflow just got faster.

---

📜 Recent review details

Configuration used: .coderabbit.yaml
Review profile: ASSERTIVE
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between e8b9f68 and 806b026.

📒 Files selected for processing (1)

• 3rd_party/benchmark (1 hunks)

⏰ Context from checks skipped due to timeout of 90000ms (51)

• GitHub Check: Codacy Static Code Analysis
• GitHub Check: build (XCode Debug with cppcheck (Apple Silicon), macos-14, Debug, macos-clang, ON, OFF)
• GitHub Check: build (GCC 13 Debug with UBSan, ubuntu-22.04, Debug, gcc, ON)
• GitHub Check: build (GCC 13 Release with UBSan, ubuntu-22.04, Release, gcc, ON)
• GitHub Check: build (GCC 13 Release, ubuntu-22.04, Release, gcc)
• GitHub Check: Codacy Static Code Analysis
• GitHub Check: build (XCode Debug with cppcheck (Apple Silicon), macos-14, Debug, macos-clang, ON, OFF)
• GitHub Check: build (GCC 13 Debug with UBSan, ubuntu-22.04, Debug, gcc, ON)
• GitHub Check: build (GCC 13 Release with UBSan, ubuntu-22.04, Release, gcc, ON)
• GitHub Check: build (GCC 13 Release, ubuntu-22.04, Release, gcc)
• GitHub Check: Codacy Static Code Analysis
• GitHub Check: build (XCode Debug with cppcheck (Apple Silicon), macos-14, Debug, macos-clang, ON, OFF)
• GitHub Check: build (GCC 13 Debug with UBSan, ubuntu-22.04, Debug, gcc, ON)
• GitHub Check: build (GCC 13 Release with UBSan, ubuntu-22.04, Release, gcc, ON)
• GitHub Check: build (GCC 13 Release, ubuntu-22.04, Release, gcc)
• GitHub Check: Codacy Static Code Analysis
• GitHub Check: build (XCode Debug with cppcheck (Apple Silicon), macos-14, Debug, macos-clang, ON, OFF)
• GitHub Check: build (GCC 13 Debug with UBSan, ubuntu-22.04, Debug, gcc, ON)
• GitHub Check: build (GCC 13 Release with UBSan, ubuntu-22.04, Release, gcc, ON)
• GitHub Check: build (GCC 13 Release, ubuntu-22.04, Release, gcc)
• GitHub Check: Codacy Static Code Analysis
• GitHub Check: build (XCode Debug with cppcheck (Apple Silicon), macos-14, Debug, macos-clang, ON, OFF)
• GitHub Check: build (GCC 13 Debug with UBSan, ubuntu-22.04, Debug, gcc, ON)
• GitHub Check: build (GCC 13 Release with UBSan, ubuntu-22.04, Release, gcc, ON)
• GitHub Check: build (GCC 13 Release, ubuntu-22.04, Release, gcc)
• GitHub Check: Codacy Static Code Analysis
• GitHub Check: build (XCode Debug with cppcheck (Apple Silicon), macos-14, Debug, macos-clang, ON, OFF)
• GitHub Check: build (GCC 13 Debug with UBSan, ubuntu-22.04, Debug, gcc, ON)
• GitHub Check: build (GCC 13 Release with UBSan, ubuntu-22.04, Release, gcc, ON)
• GitHub Check: build (GCC 13 Release, ubuntu-22.04, Release, gcc)
• GitHub Check: Codacy Static Code Analysis
• GitHub Check: build (XCode Debug with cppcheck (Apple Silicon), macos-14, Debug, macos-clang, ON, OFF)
• GitHub Check: build (GCC 13 Debug with UBSan, ubuntu-22.04, Debug, gcc, ON)
• GitHub Check: build (GCC 13 Release with UBSan, ubuntu-22.04, Release, gcc, ON)
• GitHub Check: build (GCC 13 Release, ubuntu-22.04, Release, gcc)
• GitHub Check: Codacy Static Code Analysis
• GitHub Check: build (XCode Debug with cppcheck (Apple Silicon), macos-14, Debug, macos-clang, ON, OFF)
• GitHub Check: build (GCC 13 Debug with UBSan, ubuntu-22.04, Debug, gcc, ON)
• GitHub Check: build (GCC 13 Release with UBSan, ubuntu-22.04, Release, gcc, ON)
• GitHub Check: build (GCC 13 Release, ubuntu-22.04, Release, gcc)
• GitHub Check: Codacy Static Code Analysis
• GitHub Check: build (XCode Debug with cppcheck (Apple Silicon), macos-14, Debug, macos-clang, ON, OFF)
• GitHub Check: build (GCC 13 Debug with UBSan, ubuntu-22.04, Debug, gcc, ON)
• GitHub Check: build (GCC 13 Release with UBSan, ubuntu-22.04, Release, gcc, ON)
• GitHub Check: build (GCC 13 Release, ubuntu-22.04, Release, gcc)
• GitHub Check: Codacy Static Code Analysis
• GitHub Check: build (XCode Debug with cppcheck (Apple Silicon), macos-14, Debug, macos-clang, ON, OFF)
• GitHub Check: build (GCC 13 Debug with UBSan, ubuntu-22.04, Debug, gcc, ON)
• GitHub Check: build (GCC 13 Release with ASan, ubuntu-22.04, Release, gcc, ON)
• GitHub Check: build (GCC 13 Release with UBSan, ubuntu-22.04, Release, gcc, ON)
• GitHub Check: build (GCC 13 Release, ubuntu-22.04, Release, gcc)

🔇 Additional comments (1)

3rd_party/benchmark (1)

1-1: Submodule pointer updated to v1.9.3
The benchmark subproject’s commit was bumped to 299e5928955cc62af9968370293b916f5130916f (v1.9.3). Ensure the project still builds cleanly with this version and run a quick smoke‐test of the benchmarks.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 98.35%. Comparing base (e8b9f68) to head (806b026).
Report is 2 commits behind head on master.

Additional details and impacted files

@@            Coverage Diff             @@
##           master     #792      +/-   ##
==========================================
+ Coverage   98.26%   98.35%   +0.08%     
==========================================
  Files          35       35              
  Lines        7040     7040              
==========================================
+ Hits         6918     6924       +6     
+ Misses        122      116       -6     

Flag	Coverage Δ
Debug	98.29% <ø> (+0.29%)	⬆️
Release	97.60% <ø> (-0.08%)	⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.