Bump benchmark from 12235e2 to 192ef10

[dependabot]

Bumps benchmark from 12235e2 to 192ef10.

Commits

• 192ef10 version bump to 1.9.5
• d8db2f9 Silence -Wc2y-extensions warning around COUNTER (#2108)
• aa3ed62 pin bazelversion to pre-9
• 31fae1b rename to avoid gtest warnings
• 5c55f5d clang tidy warnings
• 494a04f Bump actions/cache from 5.0.1 to 5.0.2 (#2104)
• 90ebbde Make the Benchmark class public (#2101)
• 262afc9 Bump scipy from 1.16.3 to 1.17.0 in /tools (#2103)
• a6e0a72 Bump numpy from 2.4.0 to 2.4.1 in /tools (#2102)
• 27fc2bf Bump pypa/cibuildwheel from 3.3.0 to 3.3.1 (#2100)
• Additional commits viewable in compare view

You can trigger a rebase of this PR 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)

Note
Automatic rebases have been disabled on this pull request as it has been open for over 30 days.

[dependabot]

Labels

The following labels could not be found: dependencies. Please create it before Dependabot can add it to a pull request.

Please fix the above issues or remove invalid values from dependabot.yml.

[derekste]

Resolved: the repository now defines the dependencies label requested by .github/dependabot.yml, and this pull request has been labeled accordingly. Future Dependabot updates can apply the configured label automatically.

[bigsamich]

Looks good. 192ef10 is the v1.9.5 release tag (v1.9.0 → v1.9.5, 199 commits).

The default CI job doesn't build the benchmark target, so the green check doesn't cover this bump. I built it locally with -DREDIS_ADAPTER_BENCHMARK=ON -DCMAKE_CXX_STANDARD=20, as in test-and-benchmark.yml:

• it builds and runs, and ctest is 14/14;
• together with the other two submodule bumps on the Recover owned readers across observed stream resets #111 stack, 18/18;
• no new warnings (the one -Wstringop-overflow in RedisCache.hpp also appears with v1.9.0).

Upstream now builds the library as C++17 and needs CMake ≥ 3.13, both within our requirements.

It needs a rebase (4 commits behind, and the required check is strict).

Side note: the -DCMAKE_CXX_STANDARD=20 in test-and-benchmark.yml is currently ignored, because CMakeLists.txt sets the standard as a normal variable. That workflow actually builds C++17 (#125).

[derekste]

@bigsamich Thanks for building and running the benchmark target explicitly. The regular build-test result alone doesn't cover this dependency.

After the branch is refreshed, the merge evidence should include REDIS_ADAPTER_BENCHMARK=ON, the test suite, and an actual benchmark invocation. The CMake standard override in #125 also needs correction so a C++20-labeled job really compiles as C++20. Your stack-head run is useful supporting evidence; we still need the required check on the final head.

The fixes above are in progress. I'll post the changed commits and validation before requesting another code review.

[derekste]

@bigsamich refreshed this branch against current main and kept benchmark pinned to the reviewed v1.9.5 release (192ef10025eb2c4cdd392bc502f0c852196baa48). The build now honors an explicit CMAKE_CXX_STANDARD, and the benchmark can select a private Redis endpoint with REDIS_ADAPTER_BENCHMARK_PORT.

Validation at 093edf9: native Linux C++20 build, all 14 CTest cases, and an actual benchmark smoke run covering baseline, scalar writes/reads, 256-element list writes/reads, and cache-copy cases against an isolated Redis 7.4.2 fixture. The generated compile flags contain -std=gnu++20. The macOS C++20 build also passes. These short benchmark runs verify execution; they are not a performance comparison.

Ready for another review.

[derekste]

LGTM at 093edf9. The benchmark v1.9.5 pin, explicit C++ standard override, and private benchmark-port option look consistent. The current required build-test is green; the PR also records the Linux C++20 build, all 14 CTest cases, and an actual isolated benchmark smoke run for this revision. No critical blocker found. The benchmark execution evidence comes from the posted validation; I did not rerun it in this pass.