fix(ci): use own md5 tool for Bazel 9 compatibility
#1007
+3
−2
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.
Bazel 9.0.0 flipped
--incompatible_strict_action_envtotrueby default (bazelbuild/bazel#27670), restrictingPATHto/bin:/usr/bin:/usr/local/bin.On macOS, this broke a few tests relying on the
md5sumcommand (example):This is because:
md5sumis not a native macOS command (macOS equivalent ismd5),md5sumis typically in/opt/homebrew/bin, which is no longer in the restrictedPATH.Since the repo already maintains a cross-platform
//tests/util:md5tool, the fix simply consists in leveraging it.Note on:
... is only meant to get distinct md5 sums for the 2 input files used in the tests.
Fixes #1010.