Skip to content

[9.4] [ML] Retry 3rd-party git clones and propagate clone failures (#3233) - #3235

Merged
edsavage merged 1 commit into
9.4from
backport/9.4/pr-3233
Oct 13, 2026
Merged

edsavage merged 1 commit into
9.4from
backport/9.4/pr-3233

Conversation

@elastic-vault-github-plugin-prod

Copy link
Copy Markdown
Contributor

Backport

This will backport the following commits from main to 9.4:

Questions ?

Please refer to the Backport tool documentation

The Eigen and Valijson sources are cloned at CMake configure time from
gitlab.com and github.com respectively. Those hosts occasionally return
transient errors (e.g. GitLab "currently unable to handle this request
due to load"), and a single failed clone was enough to break an entire
CI build, requiring a manual rebuild.

Wrap each clone in a bounded retry loop (5 attempts, increasing backoff)
that starts from a clean slate on every attempt, so a brief hosting
outage no longer fails the build.

Also propagate the failure from the outer execute_process() calls that
run these scripts. Previously the FATAL_ERROR raised inside the child
`cmake -P` process was swallowed: configure logged the error but
continued with an empty 3rd_party/eigen, so the failure only surfaced
much later as a cryptic "Eigen/Core: No such file or directory" compile
error. COMMAND_ERROR_IS_FATAL ANY makes configure stop immediately with
the clear message once retries are exhausted, finally delivering the
behaviour #3164 intended.

(cherry picked from commit bcce4aa)
@edsavage
edsavage enabled auto-merge (squash) October 13, 2026 02:39
@edsavage
edsavage disabled auto-merge October 13, 2026 02:39
@edsavage
edsavage merged commit 90b7f48 into 9.4 Oct 13, 2026
33 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants