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 AzureStorageServiceTests #14499

Closed
opensearch-ci-bot opened this issue Jun 21, 2024 · 9 comments
Closed
Assignees
Labels
autocut flaky-test Random test failure that succeeds on second run Plugins >test-failure Test failure from CI, local build, etc.

Comments

@opensearch-ci-bot
Copy link
Collaborator

opensearch-ci-bot commented Jun 21, 2024

Flaky Test Report for AzureStorageServiceTests

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

Details

Git Reference Merged Pull Request Build Details Test Name
4a028e7 14494 41469 org.opensearch.repositories.azure.AzureStorageServiceTests.testClientUsingManagedIdentity

The other pull requests, besides those involved in post-merge actions, that contain failing tests with the AzureStorageServiceTests 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 21, 2024
@prudhvigodithi
Copy link
Contributor

prudhvigodithi commented Jun 22, 2024

[Triage]
Hey @reta this issue is created because the commit 4a028e7 even though this was not merged but was part of github.event_name == 'push' (coming from line) and hence the post_merge_action=true, I assume this is because the commit is part of the opensearch-project/OpenSearch repo on a different branch.
@getsaurabh02

@prudhvigodithi
Copy link
Contributor

@prudhvigodithi
Copy link
Contributor

Also I can see the build https://build.ci.opensearch.org/job/gradle-check/41469/ has push trigger whitesourceremediatecomazureazureidentity1x 4a028e7883565d56f0bdb239886c4dbddf4d40d2
@andrross

@reta
Copy link
Collaborator

reta commented Jun 22, 2024

Thanks @prudhvigodithi , I will take it right away

@reta reta self-assigned this Jun 22, 2024
@reta
Copy link
Collaborator

reta commented Jun 22, 2024

Very weird, I am closing this at the moment since it does not look valid anymore

@prudhvigodithi
Copy link
Contributor

[Triage]
Until we have this in place #14475, the bot will re-open the issue, I will be working on #14475.
Thanks
@getsaurabh02

@peternied
Copy link
Member

[Triage - attendees 1 2 3]
Approving this autocut issue

@prudhvigodithi
Copy link
Contributor

Very weird, I am closing this at the moment since it does not look valid anymore

Closing this based on the comment from @reta.

@prudhvigodithi
Copy link
Contributor

prudhvigodithi commented Jun 27, 2024

The automation is in place that wont re-open the issue if there no change in the Flaky report after the issue is closed https://build.ci.opensearch.org/job/gradle-check-flaky-test-detector/60/console

Not Re-opening the issue as the no change in the Flaky report after the issue is closed

Thank you
@getsaurabh02 @andrross @reta

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 Plugins >test-failure Test failure from CI, local build, etc.
Projects
None yet
Development

No branches or pull requests

4 participants