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.

Sign up for GitHub

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

Jump to bottom

[8.15](backport #5145) [CI] Automatic retries for integration tests #5161

Closed
wants to merge 2 commits into from
Closed

[8.15](backport #5145) [CI] Automatic retries for integration tests #5161

wants to merge 2 commits into from

Conversation

mergify[bot]
Copy link
Contributor

@mergify mergify bot commented Jul 17, 2024

What does this PR do?

Each failed integration test step will be retried once

Why is it important?

Sometimes the tests are flaky. It's not the best practice but anyway we retry them manually

Checklist

  • My code follows the style guidelines of this project
  • 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/fragments using the changelog tool
  • I have added an integration test or an E2E test

Disruptive User Impact

How to test this PR locally

Related issues

Questions to ask yourself

  • How are we going to support this in production?
  • How are we going to measure its adoption?
  • How are we going to debug this?
  • What are the metrics I should take care of?
  • ...
This is an automatic backport of pull request #5145 done by [Mergify](https://mergify.com).

@pazone @mergify
[CI] Automatic retries for integration tests (#5145)
09ca537 
* [CI] Automatic retries for integration tests. New GCP SA

* Reverted SA usage

(cherry picked from commit ca726a2)
@mergify mergify bot requested a review from a team as a code owner July 17, 2024 13:21
@mergify mergify bot added the backport label Jul 17, 2024
@mergify mergify bot requested review from michalpristas and blakerouse and removed request for a team July 17, 2024 13:21
@mergify mergify bot assigned pazone Jul 17, 2024
@elastic-sonarqube Elastic SonarQube
Copy link

Quality Gate passed Quality Gate passed

Issues
0 New issues
0 Fixed issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
No data about Duplication

See analysis details on SonarQube

@pazone pazone closed this Jul 18, 2024
@mergify mergify bot deleted the mergify/bp/8.15/pr-5145 branch July 18, 2024 14:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@michalpristas michalpristas michalpristas approved these changes

@blakerouse blakerouse Awaiting requested review from blakerouse blakerouse was automatically assigned from elastic/elastic-agent-control-plane

Assignees

@pazone pazone

Labels
backport
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@michalpristas @pazone