Skip to content
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

[Filebeat] Flakey test test_input_pipeline_config #9587

Closed
andrewkroh opened this issue Dec 17, 2018 · 1 comment
Closed

[Filebeat] Flakey test test_input_pipeline_config #9587

andrewkroh opened this issue Dec 17, 2018 · 1 comment
Assignees
Labels
Filebeat Filebeat flaky-test Unstable or unreliable test cases.

Comments

@andrewkroh
Copy link
Member

Flaky Test

Stack Trace

TransportError(500, u'general_script_exception', u'[script] Too many dynamic script compilations within, max: [75/5m]; please use indexed, or scripts with parameters instead; this limit can be changed by the [script.max_compilations_rate] setting')

@andrewkroh andrewkroh added Filebeat Filebeat flaky-test Unstable or unreliable test cases. labels Dec 17, 2018
ruflin added a commit to ruflin/beats that referenced this issue Dec 18, 2018
This is a temporary fix for elastic#9587. The reason I did not skip the tests instead was that I would still like us to have tests for the pipelines running until we figured out which script is the culprit.
ruflin added a commit that referenced this issue Dec 18, 2018
This is a temporary fix for #9587. The reason I did not skip the tests instead was that I would still like us to have tests for the pipelines running until we figured out which script is the culprit.
@urso urso assigned kvch Feb 8, 2019
@andrewkroh
Copy link
Member Author

Looking back at build stats this test hasn't shown up in the logs since Feb 2019 so I think it's stable now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Filebeat Filebeat flaky-test Unstable or unreliable test cases.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants