[updatecli] update elastic stack version for testing 9.5.0-83bc5c7c-SNAPSHOT

[github-actions]

Bump elastic-stack to latest snapshot version

Update snapshot.yml

1 file(s) updated with "$1=9.5.0-83bc5c7c-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 E2E Buildkite job failed, but the available log excerpt does not include the actual failing test or assertion. The visible TestStandAloneRunningSuite subtests all pass before the package exits with FAIL, so I don’t see enough evidence for a PR code fix yet.

Remediation

• Retry the E2E job once; this may be a transient/infrastructure or log-capture issue.
• If it fails again, inspect/upload the full go test output from testing/build/test-e2e-linux.out or the complete Buildkite job log, then rerun the identified test with TEST_RUN='<failing test name>' mage test:e2e.

Investigation details

Root Cause

Inconclusive from the prefetched data. The PR only changes dev-tools/integration/.env:4, bumping the Elasticsearch snapshot from 9.5.0-0ff71b5c-SNAPSHOT to 9.5.0-83bc5c7c-SNAPSHOT, but the provided E2E log starts mid-run and never shows the failing assertion/panic/timeout.

The visible source path for the long-running section is testing/e2e/stand_alone_test.go: TestOpAMPWithUpstreamCollector starts at line 648 and TestOpAMPWithEDOTCollector starts at line 737. Both are shown as passing in the excerpt, along with the other visible TestStandAloneRunningSuite subtests.

Evidence

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

--- PASS: TestStandAloneRunningSuite (535.40s)
    --- PASS: TestStandAloneRunningSuite/TestOpAMPWithEDOTCollector (123.98s)
    --- PASS: TestStandAloneRunningSuite/TestOpAMPWithUpstreamCollector (300.36s)
    --- PASS: TestStandAloneRunningSuite/TestWithElasticsearchConnectionFailures (42.18s)
    --- PASS: TestStandAloneRunningSuite/TestWithElasticsearchConnectionFlakyness (32.52s)
FAIL
FAIL github.com/elastic/fleet-server/testing/e2e 1299.805s
Error: exit status 1

The artifact upload also reports no matching JUnit/coverage artifacts, so the failure detail was not available from the prefetched artifacts:

No files matched paths: build/*.xml;build/e2e-coverage.out
No files found matching 'build/test-*.xml'

Verification

Not run: the E2E suite requires Docker, and Docker-in-Docker is not supported in this environment.

Follow-up

I checked for prior PR comments and found none, so this is not a duplicate detective comment. I also found an existing flaky-test issue for an older OpAMP signal: killed failure, but this log excerpt does not show that signature, so I am not treating this as the same root cause.

---

What is this? | From workflow: PR Buildkite Detective

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