-
Notifications
You must be signed in to change notification settings - Fork 278
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
[Bug]: All integration tests for RPM, Debian and Windows are failing #4370
Comments
k-NN: Test with @junqiu-lei on tar for concurrent search, resolved opensearch-project/k-NN#1419. |
Resolve rpm:
|
|
IntegTest should be fully fixed now on Windows. |
Windows looks good too now: https://build.ci.opensearch.org/blue/organizations/jenkins/integ-test/detail/integ-test/7681/pipeline |
See issues: https://build.ci.opensearch.org/blue/organizations/jenkins/integ-test-opensearch-dashboards/detail/integ-test-opensearch-dashboards/5527/pipeline/
|
Should be solved by this PR: |
There seems to be a bug where Windows will run better if:
If not this then it will nearly 100% fail the manual run of Windows ftrepo directly. Very weird. |
Resolved now. |
Describe the bug
Note: This is an observation for OpenSearch only. OSD might be a different story
Recently so many changes went in related to security plugin as well as in general. We enabled integration testing to be triggered via distribution pipeline for all distributions. (Earlier it was just running for tarball)
To reproduce
All windows failed: https://build.ci.opensearch.org/blue/organizations/jenkins/integ-test/detail/integ-test/7136/pipeline
All debian failed: https://build.ci.opensearch.org/blue/organizations/jenkins/integ-test/detail/integ-test/7135/pipeline
All RPM failed: https://build.ci.opensearch.org/blue/organizations/jenkins/integ-test/detail/integ-test/7134/pipeline
Expected behavior
All tests should run. The infrastructure and test set up should be fixed.
Screenshots
If applicable, add screenshots to help explain your problem.
Host / Environment
No response
Additional context
No response
Relevant log output
No response
The text was updated successfully, but these errors were encountered: