memtier-benchmark/2.1.4 package update

[octo-sts]

[octo-sts]

⚠️ EXPERIMENTAL

Please use 👍 or 👎 on this comment to indicate if you agree or disagree with the recommendation.

To provide more detailed feedback please comment on the recommendation prefixed with /ai-verify:

e.g. /ai-verify partially helpful but I also added bash to the build environment

Gen AI suggestions to solve the build error:

• Detected Error: "fatal: bad object 370a25ea0176183eb49731d9af7bd84f512bf600"

• Error Category: Version/Configuration

• Failure Point: Git cherry-pick operation in the git-checkout step

• Root Cause Analysis: The build is failing because it's trying to cherry-pick a commit (370a25ea0176183eb49731d9af7bd84f512bf600) that either doesn't exist in the repository or is not accessible at the specified branch.

• Suggested Fix:

1. Remove the cherry-pick section from the melange YAML since it's trying to cherry-pick a version bump commit that's no longer needed:

  - uses: git-checkout
    with:
      repository: https://github.com/RedisLabs/memtier_benchmark
      tag: ${{package.version}}
      expected-commit: 4b0f5ee8b88498d6cc17fbccff9590f78e047186

• Explanation:

• The cherry-pick is attempting to apply a commit that bumped the version to 2.1.3
• Since we're now building 2.1.4, this version bump commit is no longer necessary
• The tag checkout alone will give us the correct 2.1.4 version code

• Additional Notes:

• The expected-commit hash appears correct for the 2.1.4 tag
• Cherry-picks are typically used for backporting fixes, not version bumps
• The changelog indicates this is a clean 2.1.4 release with fixes included

• References:

• https://github.com/RedisLabs/memtier_benchmark/releases/tag/2.1.4
• Revert LATENCY_HDR_SEC_SIGDIGTS to 2. Optimize summarize_current_second by using hdr_value_at_percentiles() instead of N x hdr_value_at_percentile(). RedisLabs/memtier_benchmark#295