Skip to content

Increase TestRunID suffix to 6 digits #2572

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

Open
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

kcreddy
Copy link

@kcreddy kcreddy commented May 6, 2025

While debugging integrations flaky tests, in comment it is observed that the system tests are failing because there is existing S3 bucket deployed by Terraform that is clashing with current test run.

Increasing TestRunID suffix to 6 digits to avoid clash with existing test resources.

@mrodm
Copy link
Contributor

mrodm commented May 6, 2025

@kcreddy It would be required to update the script related to system flags in order to take into account those 6 digits instead of 5 in the regexex here:

DEFAULT_AGENT_CONTAINER_NAME="elastic-package-service-[0-9]{5}-docker-custom-agent"
service_deployer_type="docker"
service_prefix='elastic-package-service-[0-9]{5}'

@elasticmachine
Copy link
Collaborator

💚 Build Succeeded

History

cc @kcreddy

@kcreddy
Copy link
Author

kcreddy commented May 6, 2025

test integrations

@elastic-vault-github-plugin-prod

Created or updated PR in integrations repository to test this version. Check elastic/integrations#13801

@kcreddy kcreddy requested a review from jsoriano May 13, 2025 06:35
@kcreddy kcreddy added the flaky-test Unstable or unreliable test cases. label May 13, 2025
@kcreddy kcreddy requested review from mrodm and removed request for a team May 13, 2025 06:42
@jsoriano
Copy link
Member

Is this change required at the end?

@kcreddy
Copy link
Author

kcreddy commented May 15, 2025

Is this change required at the end?

@jsoriano, not completely sure if this fixes the problem in elastic/integrations#13432 (and all related issues). We are not able to find the root cause, and @mrodm (in this comment) also verified the builds running at the same time and confirmed there is no retry.
Would appreciate your input in resolving this flaky test.

cc: @narph

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

Successfully merging this pull request may close these issues.

4 participants