[updatecli] update elastic stack version for testing 9.6.0-bc10acdd-SNAPSHOT

[github-actions]

Bump elastic-stack to latest snapshot version

Update snapshot.yml

1 file(s) updated with "$1=9.6.0-bc10acdd-SNAPSHOT": * dev-tools/integration/.env

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

The failing Buildkite step is an E2E timeout/failure in TestStandAloneRunningSuite/TestOpAMPWithUpstreamCollector, and the PR diff itself is not the direct cause. Immediate action is to re-run the E2E job; if it reproduces, treat it as the known OpAMP upstream-collector flake/timeout pattern and adjust that test path.

Remediation

• Re-run E2E Test for build https://buildkite.com/elastic/fleet-server/builds/16719 to confirm whether this is transient.
• If it reproduces, stabilize testing/e2e/stand_alone_test.go by removing heavy upstream build work from the per-test critical path (or increasing timeout/caching), especially around:
  • context.WithTimeout(..., 5*time.Minute) at testing/e2e/stand_alone_test.go:653
  • git clone of opentelemetry-collector-contrib at testing/e2e/stand_alone_test.go:672-680
  • make otelcontribcol at testing/e2e/stand_alone_test.go:688-693

Investigation details

Root Cause

E2E Test failed because TestStandAloneRunningSuite/TestOpAMPWithUpstreamCollector did not complete successfully within its execution window (300.28s), which aligns with this test’s 5-minute context timeout. This test does expensive work inline (clone upstream collector repo + build otelcontribcol) before enrollment assertions, so it is sensitive to runner performance and network/build variability.

This PR (#7778) changes only dev-tools/integration/.env (snapshot version bump), and does not modify E2E test logic, OpAMP code paths, or Buildkite scripts.

Evidence

• Build: https://buildkite.com/elastic/fleet-server/builds/16719
• Job/step: E2E Test (.buildkite/scripts/e2e_test.sh)
• Key log excerpt:

  --- FAIL: TestStandAloneRunningSuite (622.73s)
      --- FAIL: TestStandAloneRunningSuite/TestOpAMPWithUpstreamCollector (300.28s)
  FAIL github.com/elastic/fleet-server/testing/e2e
  Error: exit status 1
  

• Relevant source context:
  • testing/e2e/stand_alone_test.go:653 (5-minute timeout)
  • testing/e2e/stand_alone_test.go:672-680 (clone upstream contrib repo)
  • testing/e2e/stand_alone_test.go:688-693 (build upstream collector via make)

Verification

• Not run locally in this detective workflow; conclusion is based on Buildkite artifacts and repository source inspection.

Follow-up

• There is an open flaky-test issue tracking this failure family: [Flaky Test] TestStandAloneRunningSuite/TestOpAMP signal: killed #6590 (TestStandAloneRunningSuite/TestOpAMP with timeout/kill symptoms in the same OpAMP upstream collector flow).
• This run’s provided log does not include the inner assertion/stack frame for the failing subtest, so if the rerun fails again, capture the full verbose subtest traceback for exact failing line confirmation.

---

What is this? | From workflow: PR Buildkite Detective

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