[updatecli] update elastic stack version for testing 9.3.3-e780d8d6

[github-actions]

Bump elastic-stack to latest snapshot version

Update snapshot.yml

1 file(s) updated with "$1:9.3.3-e780d8d6-SNAPSHOT": * testing/environments/snapshot.yml

GitHub Action workflow link

---

Created automatically by Updatecli Options: Most of Updatecli configuration is done via its manifest(s). If you close this pull request, Updatecli will automatically reopen it, the next time it runs. If you close this pull request and delete the base branch, Updatecli will automatically recreate it, erasing all previous commits made. Feel free to report any issues at github.com/updatecli/updatecli. If you find this tool useful, do not hesitate to star our GitHub repository as a sign of appreciation, and/or to tell us directly on our chat!

[github-actions]

TL;DR

Buildkite failed before any Beat-specific build/test logic ran: multiple jobs could not clone/fetch elastic/beats due to repeated remote: Internal Server Error (HTTP 500) from GitHub during checkout/post-checkout. Immediate action is to re-run once GitHub checkout is healthy.

Remediation

• Re-run the failed Buildkite jobs/build after GitHub access stabilizes; this appears transient infra/network-side, not a PR code regression.
• If it recurs, add retry/backoff around checkout/post-checkout fetch in CI bootstrap and capture GitHub status incident correlation.

Investigation details

Root Cause

Failure class: Infrastructure (transient external dependency).

Across 9 failed jobs, the common error is checkout failure (exit status 128) caused by GitHub returning HTTP 500 on clone/fetch operations. In jobs that reached repository hooks, .buildkite/hooks/post-checkout executes:

• .buildkite/hooks/post-checkout:15 → git fetch -v origin "\$\{target_branch}"

That fetch step also fails with the same HTTP 500, confirming the failure happens in repository retrieval, before project-specific tests/build steps.

Evidence

• Build: https://buildkite.com/elastic/beats/builds/43306
• Example jobs/steps:
  • Upload Pipeline: .buildkite/filebeat/filebeat-pipeline.yml
  • Upload Pipeline: .buildkite/libbeat/pipeline.libbeat.yml
• Key log excerpts:
  • remote: Internal Server Error
  • fatal: unable to access 'https://github.com/elastic/beats.git/': The requested URL returned error: 500
  • Error: cloning git repository: exit status 128
  • Error: running "repository post-checkout" shell hook: The repository post-checkout hook exited with status 128

Verification

• Local tests/builds were not run because CI failed during checkout/bootstrap phase.
• Reviewed all listed failed Buildkite logs from /tmp/gh-aw/buildkite-logs/*; failures are consistent and identical in failure mode.

Follow-up

• If re-run still fails, collect a timestamped sample of failing GitHub clone/fetch requests and open/attach infra incident context.

Note

🔒 Integrity filtering filtered 1 item

Integrity filtering activated and filtered the following item during workflow execution.
This happens when a tool call accesses a resource that does not meet the required integrity or secrecy level of the workflow.

• pr:[updatecli] update elastic stack version for testing 9.3.3-e780d8d6 #49816 (pull_request_read: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".)

---

What is this? | From workflow: PR Buildkite Detective

Give us feedback! React with 🚀 if perfect, 👍 if helpful, 👎 if not.

[mergify]

Automatically approving mergify

[mergify]

Merge Queue Status

• ✅ Entered queue — 2026-04-01 08:41 UTC · Rule: default
• ✅ Checks started · on draft merge queue: embarking 9.3 (ba5c2e8) and #49816 together #49832
• 🚫 Left the queue — 2026-04-01 08:47 UTC · at 739082591fb015da1a8e48fd931ee64db088059c

This pull request spent 6 minutes 14 seconds in the queue, including 36 seconds running CI.

Required conditions to merge

• check-success=CLA
• check-success=buildkite/beats
• any of [🛡 GitHub branch protection]:
  • check-neutral = CLA
  • check-skipped = CLA
  • check-success = CLA
• any of [🛡 GitHub branch protection]:
  • check-neutral = buildkite/beats
  • check-skipped = buildkite/beats
  • check-success = buildkite/beats
• #approved-reviews-by >= 1 [🛡 GitHub branch protection]
  • [updatecli] update elastic stack version for testing 9.3.3-e780d8d6 #49816
• #approved-reviews-by >= 1 [🛡 GitHub repository ruleset rule [org] Require a PR for Renovate]
  • [updatecli] update elastic stack version for testing 9.3.3-e780d8d6 #49816
• #approved-reviews-by >= 1 [🛡 GitHub repository ruleset rule [org] Require a PR]
  • [updatecli] update elastic stack version for testing 9.3.3-e780d8d6 #49816
• #changes-requested-reviews-by = 0 [🛡 GitHub branch protection]
  • [updatecli] update elastic stack version for testing 9.3.3-e780d8d6 #49816
• #changes-requested-reviews-by = 0 [🛡 GitHub repository ruleset rule [org] Require a PR for Renovate]
  • [updatecli] update elastic stack version for testing 9.3.3-e780d8d6 #49816
• #changes-requested-reviews-by = 0 [🛡 GitHub repository ruleset rule [org] Require a PR]
  • [updatecli] update elastic stack version for testing 9.3.3-e780d8d6 #49816

Reason

New commits have been added to the draft pull request that were not made by Mergify

Hint

If you want to requeue this pull request, you can post a @mergifyio queue comment.