-
Notifications
You must be signed in to change notification settings - Fork 154
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
BK Integration tests: fix retry usage #5760
Conversation
This pull request does not have a backport label. Could you fix it @pazone? 🙏
|
|
I'll sign off when I see the results of CI and the test run pass: https://buildkite.com/elastic/elastic-agent-extended-testing-bk |
@pazone More fixes are needed. The test run has been hanging for 2.5 hours with this repeated message. I'm canceling the run.
|
Added a few more commits. Now it works. Here is the example build |
|
* Integration tests: fix retry usage * Integration tests: fix retry usage * Correct terraform version * Correct terraform version * Correct terraform version * Correct terraform version * Correct terraform version * Pin agent version * Pin agent version (cherry picked from commit 431b094)
* Integration tests: fix retry usage * Integration tests: fix retry usage * Correct terraform version * Correct terraform version * Correct terraform version * Correct terraform version * Correct terraform version * Pin agent version * Pin agent version (cherry picked from commit 431b094)
* Integration tests: fix retry usage * Integration tests: fix retry usage * Correct terraform version * Correct terraform version * Correct terraform version * Correct terraform version * Correct terraform version * Pin agent version * Pin agent version (cherry picked from commit 431b094) Co-authored-by: Pavel Zorin <pavel.zorin@elastic.co>
What does this PR do?
Why is it important?
Checklist
./changelog/fragments
using the changelog toolDisruptive User Impact
How to test this PR locally
Related issues
Questions to ask yourself