-
Notifications
You must be signed in to change notification settings - Fork 976
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
[ACTION NEEDED] Fix flaky integration tests at distribution level #6337
Comments
Flakey test from 2.13: #6373, opensearch-project/opensearch-dashboards-functional-test#1210 |
@ashwin-pc @AMoo-Miki Can you please provide your inputs? |
Both the tests should already be resolved. Will let @kavilla reply once he verifies it |
Adding 2.14.0 release manager @rishabh6788 |
Checked previously and passing will make check when RC is ran. |
Re-tagging the issue with upcoming 2.19 release. Please close if the issue is resolved. Thanks! |
@kavilla can we close this? |
I think we are still seeing flaky tests for ci-group 2 and ci-group 6 |
Can you link to the specific test failures? We are also tracking CI group failures across OSD core. I want to see if there is an overlap |
See the dashboard here for all the tests data. I tried filtering it for 2.19.0 ci-group-6 For 3.0.0-alpha1, @peterzhuamazon is yet to run the tests I believe. Informed it offline. He will update once those results are in. |
Just an update, 3.0.0 is still pending a fix for opensearch-project/security-analytics-dashboards-plugin#1185 so we are not able to run any OSD tests. We are working closely with the plugin owner of SA Dash to fix that. Thanks. |
@gaiksaya based on the dashboard you shared, Ci group 6 has been stable for a few weeks now. Anything im missing? ![]() |
We did not run 2.19.0 tests after it was released. Last run was on Feb 10, 2025 Here is similar one for current release |
What is the bug?
It was observed in 2.13.0 and previous other releases that this component manually signed off on the release for failing integration tests. See opensearch-project/opensearch-build#4433 (comment)
The flakiness of the test runs take a lot of time from the release team to collect go/no-go decision and significantly lower the confidence in the release bundles.
How can one reproduce the bug?
Steps to reproduce the behavior:
What is the expected behavior?
Tests should be consistently passing.
Do you have any additional context?
Please note that this is a hard blocker for 2.14.0 release as per the discussion here
The text was updated successfully, but these errors were encountered: