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

[AUTOCUT] Gradle Check Flaky Test Report for VerifyVersionConstantsIT #14585

Open
opensearch-ci-bot opened this issue Jun 27, 2024 · 2 comments
Open

[AUTOCUT] Gradle Check Flaky Test Report for VerifyVersionConstantsIT #14585

opensearch-ci-bot opened this issue Jun 27, 2024 · 2 comments
Labels
autocut Build Build Tasks/Gradle Plugin, groovy scripts, build tools, Javadoc enforcement. flaky-test Random test failure that succeeds on second run Libraries Lucene Upgrades and Libraries, Any 3rd party library that Core depends on, ex: nebula; team is respo >test-failure Test failure from CI, local build, etc.

Comments

@opensearch-ci-bot
Copy link
Collaborator

opensearch-ci-bot commented Jun 27, 2024 •
edited
Loading

Flaky Test Report for VerifyVersionConstantsIT

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

Details

Git Reference Merged Pull Request Build Details Test Name
62b1537 16238 49097 org.opensearch.qa.verify_version_constants.VerifyVersionConstantsIT.testLuceneVersionConstant
acf209f 16216 49106 org.opensearch.qa.verify_version_constants.VerifyVersionConstantsIT.testLuceneVersionConstant
b5917c5 16227 49099 org.opensearch.qa.verify_version_constants.VerifyVersionConstantsIT.testLuceneVersionConstant
d9e9944 14562 41749 org.opensearch.qa.verify_version_constants.VerifyVersionConstantsIT.testLuceneVersionConstant

The other pull requests, besides those involved in post-merge actions, that contain failing tests with the VerifyVersionConstantsIT 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 Jun 27, 2024
@andrross
Copy link
Member

andrross commented Jun 27, 2024 •
edited
Loading

I believe implementing opensearch-project/opensearch-build-libraries#420 will fix this issue. See #12407 for more context.

@SwethaGuptha SwethaGuptha mentioned this issue Jul 1, 2024
Merged
3 tasks
@peternied
Copy link
Member

[Triage - attendees 1 2 3]
Automatically approving autocut issue

@peternied peternied added Build Build Tasks/Gradle Plugin, groovy scripts, build tools, Javadoc enforcement. Libraries Lucene Upgrades and Libraries, Any 3rd party library that Core depends on, ex: nebula; team is respo and removed untriaged labels Jul 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
autocut Build Build Tasks/Gradle Plugin, groovy scripts, build tools, Javadoc enforcement. flaky-test Random test failure that succeeds on second run Libraries Lucene Upgrades and Libraries, Any 3rd party library that Core depends on, ex: nebula; team is respo >test-failure Test failure from CI, local build, etc.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@peternied @andrross @opensearch-ci-bot