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

[AUTOCUT] Gradle Check Flaky Test Report for IngestCommonClientYamlTestSuiteIT #15837

Closed
opensearch-ci-bot opened this issue Sep 6, 2024 · 1 comment
Labels
autocut flaky-test Random test failure that succeeds on second run >test-failure Test failure from CI, local build, etc. untriaged

Comments

@opensearch-ci-bot
Copy link
Collaborator

Flaky Test Report for IngestCommonClientYamlTestSuiteIT

Noticed the IngestCommonClientYamlTestSuiteIT has some flaky, failing tests that failed during post-merge actions.

Details

Git Reference Merged Pull Request Build Details Test Name
691f78c 14998 43570 org.opensearch.ingest.common.IngestCommonClientYamlTestSuiteIT.test {yaml=ingest/70_bulk/Test bulk upsert honors default_pipeline and final_pipeline when the auto-created index matches with the index template}
f03dde9 15160 44258 org.opensearch.ingest.common.IngestCommonClientYamlTestSuiteIT.test {yaml=ingest/70_bulk/Test bulk upsert honors default_pipeline and final_pipeline when the auto-created index matches with the index template}

The other pull requests, besides those involved in post-merge actions, that contain failing tests with the IngestCommonClientYamlTestSuiteIT class are:

For more details on the failed tests refer to OpenSearch Gradle Check Metrics dashboard.

@opensearch-ci-bot opensearch-ci-bot added >test-failure Test failure from CI, local build, etc. autocut flaky-test Random test failure that succeeds on second run untriaged labels Sep 6, 2024
@gaobinlong
Copy link
Collaborator

Fixed by #15162.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
autocut flaky-test Random test failure that succeeds on second run >test-failure Test failure from CI, local build, etc. untriaged
Projects
None yet
Development

No branches or pull requests

2 participants