-
Notifications
You must be signed in to change notification settings - Fork 274
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
Split OSD tests by CI group #4745
Comments
Will discuss with the team regarding the split of cgroups through test_finder.sh before adding components in OSD test manifest. Thanks. All PRs: FT Repo:
Build Repo |
Current metrics:
We have noticed when running OSD core integTest, after entering Security test mode it took nearly 2hrs to reach 27/57 test cases. This next test case also seems hang as after 36min it still didnt move to another. Thanks. |
When trying to use
It was suggested by team to reduce the defaultCommandTimeout from 60s to 10s in this PR: https://github.com/opensearch-project/opensearch-dashboards-functional-test/pull/1418/files#diff-db1f8bb89a89d5b089b39a2af3c27ab75092f1844a158eca0a76445d513d9044 It was later discovered that above change has failed many other OSD plugins tests as documented in opensearch-project/OpenSearch#14442, therefore we revert the above change in opensearch-project/opensearch-dashboards-functional-test#1421. There are 2 approaches right now to resolve this:
Thanks. |
After doing the following changes we now see a consistent failure on this error on NOSEC on ARM64/X64 TAR.
The previous comments vis builder related errors are resolved after combing #4796 and 10s reduce on defaultCommandTimeout. |
After more tries I realize my initial implementation of changing 60s to 10s is noop due to cypress only accept int instead of str as value type for This means if we apply the 10s correctly, the test will immediately fail from the start due to not enough wait:
So we back to use 60s for all test. |
We have identified that the ftrepo is using |
More updates: Related to this: opensearch-project/OpenSearch-Dashboards#6970 it seems like. cc: @AMoo-Miki to take a look on this. |
Create issue: |
More Windows issues after applying the .gitattributes to fix json formatting:
|
Adding multiple fixes to the OSD Core related issues in ftrepo here, thanks @AMoo-Miki for providing help on Windows section. |
Apparently this PR is missed in backports, thus showing all these errors here: cc: @ashwin-pc @abbyhu2000 |
More fixes on the deb and rpm integtests: |
After @rishabh6788 and @peterzhuamazon changes we now able to run green end-to-end integTest on Jenkins with ci groups. Can we close this issue for now @ashwin-pc ? Thanks. |
Do we have a follow up issue to improve this since you guys weren't happy manually configuring the ci groups in multiple places? |
From infra team's perspective the ci-group # is handled in test manifest, see https://github.com/opensearch-project/opensearch-build/blob/main/manifests/2.15.0/opensearch-dashboards-2.15.0-test.yml#L21. So in future if any No more action items as of now. |
As the new issue is created now in OSD core, we will close this old issue as it has been implemented in 2.15.0. Thanks. |
Is your feature request related to a problem? Please describe
Currently OSD tests are run all together. OSD has a lot of tests that when all run together fail consistently.
Describe the solution you'd like
We should split the OSD tests by CI groups similar to the OSD CI and now the FTR CI as well
Describe alternatives you've considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: