-
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
Enabling retries for Beats flaky tests #39174
Enabling retries for Beats flaky tests #39174
Conversation
1710f61
to
45202b2
Compare
26e67cc
to
cba2948
Compare
As per global Jenkinsfile Cloud tests are not retried. But there is no context provided why it's failure is legit, as well as not clear if that statement is still actual. As of now Cloud tests won't be retried for |
2d3194c
to
2e760a5
Compare
2e760a5
to
75843bb
Compare
Do I understand the PR correctly and you are adding retries to every step? (besides the ones you mentioned explicitly you are not) |
75843bb
to
49102e9
Compare
I have added retries to same steps as it is in Jenkins. |
4f31e21
to
6e71cc6
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I noticed that we aren't touching/adding retries to the deploy-k8s-pipeline
, is there a reason for that?
Also left a few minor questions. Otherwise this looks ready to be shipped.
c2e8f04
to
0f9fbb2
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
/test |
0f9fbb2
to
4aae98c
Compare
d630cb4
to
10fda65
Compare
* added retries for auditbeat flaky tests * added retries for filebeat flaky tests * added retries * test exitcode * checged exit status code for retries * set larger timeout for pytestOpts * restored timeout for pytests (cherry picked from commit 02ea29d)
* added retries for auditbeat flaky tests * added retries for filebeat flaky tests * added retries * test exitcode * checged exit status code for retries * set larger timeout for pytestOpts * restored timeout for pytests (cherry picked from commit 02ea29d) # Conflicts: # .buildkite/packetbeat/pipeline.packetbeat.yml # .buildkite/winlogbeat/pipeline.winlogbeat.yml # .buildkite/x-pack/pipeline.xpack.heartbeat.yml # .buildkite/x-pack/pipeline.xpack.libbeat.yml # .buildkite/x-pack/pipeline.xpack.osquerybeat.yml # .buildkite/x-pack/pipeline.xpack.packetbeat.yml # .buildkite/x-pack/pipeline.xpack.winlogbeat.yml
* added retries for auditbeat flaky tests * added retries for filebeat flaky tests * added retries * test exitcode * checged exit status code for retries * set larger timeout for pytestOpts * restored timeout for pytests (cherry picked from commit 02ea29d)
This reverts commit e985f41.
(cherry picked from commit 02ea29d) Co-authored-by: Olga Naydyonock <[email protected]>
(cherry picked from commit 02ea29d) Co-authored-by: Olga Naydyonock <[email protected]>
(cherry picked from commit 02ea29d) --------- Co-authored-by: Olga Naydyonock <[email protected]> Co-authored-by: Dimitrios Liappis <[email protected]>
Proposed commit message
In scope of beats migration from Jenkins to Buildkite - added retries to tests (Cloud tests not retried at the moment, see comment below).
Packaging, K8Tests are not retried according to global Jenkinsfile.
BK Builds: https://buildkite.com/elastic/beats/builds?branch=oakrizan%3Aenable-retries-for-flaky-tests
Auditbeat MacOS test failure not related/caused by current PR. Related issue: https://github.com/elastic/ingest-dev/issues/3268
Checklist
CHANGELOG.next.asciidoc
orCHANGELOG-developer.next.asciidoc
.Author's Checklist
How to test this PR locally
Related issues
Use cases
Screenshots
Logs