Skip to content

Fail CMake configure if 3rd-party git clone fails (#3164) (#9.4) - #3166

Closed
edsavage wants to merge 2 commits into
elastic:9.4from
edsavage:fix/harden-cmake-clones-9.4
Closed

Fail CMake configure if 3rd-party git clone fails (#3164) (#9.4)#3166
edsavage wants to merge 2 commits into
elastic:9.4from
edsavage:fix/harden-cmake-clones-9.4

Conversation

@edsavage

Copy link
Copy Markdown
Contributor

Backport of #3164 to 9.4.

Adds RESULT_VARIABLE checking to both pull-eigen.cmake and pull-valijson.cmake. On 9.4, both Eigen and Valijson are cloned at CMake configure time; the 9.4 snapshot build on 2026-08-30 failed because GitLab was overloaded when Eigen was being cloned, and CMake continued silently.

🤖 Generated with Claude Code

edsavage and others added 2 commits August 31, 2026 09:39
Previously, execute_process() silently ignored a non-zero exit from the
git clone command. If the GitLab server is unavailable or overloaded,
CMake would continue configuring with no Eigen headers present, leading
to a cryptic compiler error hundreds of lines later instead of a clear
configure-time failure.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Same hardening as pull-eigen.cmake: report a clear configure-time error
if the git clone fails rather than silently continuing and producing a
cryptic compiler error later.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
@edsavage

Copy link
Copy Markdown
Contributor Author

Closing in favour of auto-backport from #3164 after merge.

@edsavage edsavage closed this Aug 30, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants