[Flaky test] Skip TestEndpointLogsAreCollectedInDiagnostics #4450
Conversation
This file contains 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
|
Pinging @elastic/elastic-agent (Team:Elastic-Agent) |
|
Closing due to the existing fix #4453 |
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?
Skip TestEndpointLogsAreCollectedInDiagnostics
Why is it important?
By skipping flaky tests, we're ushering in a new era of productivity, where teams can focus on delivering high-quality features without the hindrance of unreliable testing outcomes. Streamlining the development process, we optimize resource utilization, ensuring that valuable time and computing power are directed towards areas that truly matter. Our commitment to fostering a culture of trust means stakeholders can rely on accurate testing results to make informed decisions, accelerating time-to-market and giving your product a competitive edge. With increased confidence in testing outcomes, improved developer morale, and aligned testing strategies, we're not just skipping tests – we're embracing continuous improvement and shaping the future of software testing.
Checklist
[ ] I have commented my code, particularly in hard-to-understand areas[ ] 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 testHow to test this PR locally
TestEndpointLogsAreCollectedInDiagnosticswill be skippedRelated issues
Questions to ask yourself