[8.19][Automation] Update elastic/beats to 972ccf0abf8b #11729
+599
−48
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
github-actions
bot
requested review from
michel-laterman and
ycombinator
and removed request for
a team
github-actions
bot
added
Team:Elastic-Agent-Control-Plane
Contributor
|
Pinging @elastic/elastic-agent-control-plane (Team:Elastic-Agent-Control-Plane) |
ycombinator
previously approved these changes
Dec 10, 2025
github-actions
bot
changed the title
Member
|
Current testing failures: beat_receivers_test.go:1649:
--
Error Trace: /opt/buildkite-agent/builds/bk-agent-prod-gcp-1765476603219584926/elastic/elastic-agent/testing/integration/ess/beat_receivers_test.go:1118
/opt/buildkite-agent/builds/bk-agent-prod-gcp-1765476603219584926/elastic/elastic-agent/testing/integration/ess/beat_receivers_test.go:1653
/opt/buildkite-agent/.asdf/installs/golang/1.24.11/go/src/runtime/asm_amd64.s:1700
Error: Not equal:
expected: 3
actual : 0
beat_receivers_test.go:1649:
Error Trace: /opt/buildkite-agent/builds/bk-agent-prod-gcp-1765476603219584926/elastic/elastic-agent/testing/integration/ess/beat_receivers_test.go:1649
/opt/buildkite-agent/builds/bk-agent-prod-gcp-1765476603219584926/elastic/elastic-agent/testing/integration/ess/beat_receivers_test.go:1766
Error: Condition never satisfied
Test: TestMonitoringNoDuplicates
fixture.go:829: >> running binary with: [/opt/Elastic/Agent/elastic-agent status --output json]
fixture_install.go:306: [test TestMonitoringNoDuplicates] Inside fixture cleanup function
fixture_install.go:322: collecting diagnostics; test failed |
github-actions
bot
changed the title
Made with ❤️️ by updatecli
Made with ❤️️ by updatecli
Made with ❤️️ by updatecli
swiatekm
force-pushed
the
updatecli_8.19_updatecli-update-beats-8.19
branch
from
ffc4471 to
84bc08e
Compare
Contributor
|
These failures are quite mysterious. They appear to be consistent, and it looks like the coordinator deadlocks. But I've no clue how the changes in this PR could lead to that, or what's actually going on. |
Contributor
⏳ Build in-progress, with failures
Failed CI Steps
History
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What
Update
elastic/beatsto the latest version on branch8.19.Changeset
Bump beats
Update to elastic/beats@972ccf0abf8b
ran shell command ".ci/scripts/update-beats.sh 972ccf0abf8b"
Created automatically by Updatecli
Options:
Most of Updatecli configuration is done via its manifest(s).
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!