Fix cold build reproducibility - #182
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Description
Fix cold builds on development hosts where the active JDK is installed outside a standard system path and
JAVA_HOMEis unset.The S3-RDMA CMake task now receives the exact JDK home used to run Gradle, allowing CMake
FindJNIto locate headers consistently. This also records the complete Go workspace checksums resolved by the repository-pinned Go 1.25.10 toolchain after a cold module-cache rebuild.Tested on Linux amd64 with Go 1.25.10, Temurin JDK 21.0.12.1, CMake 4.3.0, and Docker 29.7.2.