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: "Expected commit 80fa7c7c69b395c81385dd56fd2408c0f2564c68 for 2.1.4, found cc6cbb7e23115b4b90db472446cbdfcef2d9ba9c"

• Error Category: Version/Commit Hash Mismatch

• Failure Point: git-checkout step in the pipeline

• Root Cause Analysis: The expected commit hash in the melange YAML doesn't match the actual commit hash for the 2.1.4 tag in the upstream repository

• Suggested Fix: Update the expected-commit hash in the git-checkout step:

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

• Explanation: The build system verifies the integrity of the source code by checking the commit hash. The current hash in the YAML file is incorrect for tag 2.1.4. Updating to the correct hash will allow the checkout to proceed.

• Additional Notes:

• This is a common issue when package versions are updated
• The correct commit hash can be verified using:
  git ls-remote https://github.com/RedisLabs/memtier_benchmark refs/tags/2.1.4
• Always verify commit hashes when updating package versions

• References:

• https://github.com/RedisLabs/memtier_benchmark/releases/tag/2.1.4
• RedisLabs/memtier_benchmark@cc6cbb7