-
Notifications
You must be signed in to change notification settings - Fork 4.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cherry-pick #20999 to 7.x: [Beats][pytest] Asserting if filebeat logs include errors #21554
Conversation
) First iteration on tackling this issue, allowing to assert on errors in filebeat, since any test will fail afterwards anyway, and the logs should not include errors. This could be anything from Elasticsearch not being available to pipeline failing to install. (cherry picked from commit 4dd8061)
Pinging @elastic/integrations-services (Team:Services) |
Pinging @elastic/integrations-platforms (Team:Platforms) |
💔 Tests FailedExpand to view the summary
Build stats
Test stats 🧪
Test errorsExpand to view the tests failures
Steps errorsExpand to view the steps failures
Log outputExpand to view the last 100 lines of log output
|
Cherry-pick of PR #20999 to 7.x branch. Original message:
What does this PR do?
First iteration on tackling this issue, allowing to assert on errors in filebeat, since any test will fail afterwards anyway, and the logs should not include errors. This could be anything from Elasticsearch not being available to pipeline failing to install.
Why is it important?
Ensure that a test is failing with the correct errors, currently if anything in the logs return an error, assertion will only include that it was a timeout, but it's actually an issue with for example pipeline installation.
- [ ] I have added an entry inCHANGELOG.next.asciidoc
orCHANGELOG-developer.next.asciidoc
.Link related issues below. Insert the issue link or reference after the word "Closes" if merging this should automatically close it.