Ensure we don't report output status in tests where it's irrelevant #11257
+4
−0
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
In some tests, we use a nonexistent ES host to avoid needing to use a remote. Output health reporting actually works for beats receivers, so this can lead to flakiness due to components reporting a degraded state. Disable the status reporting where it's irrelevant to the test.
swiatekm
added
chore
Contributor
|
This pull request does not have a backport label. Could you fix it @swiatekm? 🙏
|
swiatekm
added
the
Team:Elastic-Agent-Control-Plane
Contributor
|
Pinging @elastic/elastic-agent-control-plane (Team:Elastic-Agent-Control-Plane) |
blakerouse
approved these changes
Nov 19, 2025
pchila
approved these changes
Nov 19, 2025
Contributor
|
@Mergifyio backport 8.19 9.1 9.2 |
Contributor
✅ Backports have been created
|
mergify bot
pushed a commit
that referenced
this pull request
Nov 19, 2025
…11257) In some tests, we use a nonexistent ES host to avoid needing to use a remote. Output health reporting actually works for beats receivers, so this can lead to flakiness due to components reporting a degraded state. Disable the status reporting where it's irrelevant to the test. (cherry picked from commit 1fa0972)
Contributor
💛 Build succeeded, but was flaky
Failed CI Steps
cc @swiatekm |
Closed
3 tasks
mergify bot
pushed a commit
that referenced
this pull request
Nov 19, 2025
…11257) In some tests, we use a nonexistent ES host to avoid needing to use a remote. Output health reporting actually works for beats receivers, so this can lead to flakiness due to components reporting a degraded state. Disable the status reporting where it's irrelevant to the test. (cherry picked from commit 1fa0972)
mergify bot
pushed a commit
that referenced
this pull request
Nov 19, 2025
…11257) In some tests, we use a nonexistent ES host to avoid needing to use a remote. Output health reporting actually works for beats receivers, so this can lead to flakiness due to components reporting a degraded state. Disable the status reporting where it's irrelevant to the test. (cherry picked from commit 1fa0972)
swiatekm
added a commit
that referenced
this pull request
Nov 19, 2025
…11257) (#11261) In some tests, we use a nonexistent ES host to avoid needing to use a remote. Output health reporting actually works for beats receivers, so this can lead to flakiness due to components reporting a degraded state. Disable the status reporting where it's irrelevant to the test. (cherry picked from commit 1fa0972) Co-authored-by: Mikołaj Świątek <mail@mikolajswiatek.com>
hayotbisonai
pushed a commit
to hayotbisonai/elastic-agent
that referenced
this pull request
Nov 23, 2025
…lastic#11257) In some tests, we use a nonexistent ES host to avoid needing to use a remote. Output health reporting actually works for beats receivers, so this can lead to flakiness due to components reporting a degraded state. Disable the status reporting where it's irrelevant to the test.
3 tasks
This was referenced Dec 3, 2025
Merged
Closed
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 does this PR do?
In some tests, we use a nonexistent ES host to avoid needing to use a remote. Output health reporting actually works for beats receivers, so this can lead to flakiness due to components reporting a degraded state. Disable the status reporting where it's irrelevant to the test.
Why is it important?
Tests shouldn't randomly fail because the output correctly reports a degraded status.
Checklist
[ ] I have made corresponding changes to the documentation[ ] I have made corresponding change to the default configuration files[ ] I have added tests that prove my fix is effective or that my feature works[ ] I have added an entry in./changelog/fragmentsusing the changelog tool[ ] I have added an integration test or an E2E testRelated issues