-
Notifications
You must be signed in to change notification settings - Fork 115
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
CI failed on dashboards-search-relevance with TCP ECONNRESET #902
Comments
Hi @noCharger , it seems that the issue has something to do with build process of OSD core, and I created a dummy PR opensearch-project/dashboards-search-relevance#316 in your repo and it turned out to work well, please retry to see if it has solved your problem. |
@SuZhou-Joe Could you share more details about this build process change?
I saw the CI passed, would you mind turn it into review so we can get it merged? |
Sure, open it as ready for review. |
@SuZhou-Joe I suppose this workflow failure related to this issue as well? https://github.com/opensearch-project/opensearch-dashboards-functional-test/actions/runs/6466652988/job/17557912064?pr=736 |
I thought they were the same but actually not, search relevance CI runs on Node v14, which is OK when OSD start on |
Should be fixed by #960 so I am going to close this issue. |
What is the bug?
A clear and concise description of the bug.
CI failed on dashboards-search-relevance with TCP ECONNRESET
How can one reproduce the bug?
Steps to reproduce the behavior.
This only happening on CI. Ex: https://github.com/opensearch-project/dashboards-search-relevance/actions/runs/6280962123/job/17359747615?pr=267
What is the expected behavior?
A clear and concise description of what you expected to happen.
CI pass
What is your host/environment?
Operating system, version.
ubuntu-latest, 11
Do you have any additional context?
Add any other context about the problem.
A potential change to ignore such failures
https://github.com/hilleer/vscode-yaml-plus-json/pull/146/files#diff-2785793ab42443fdaafae000e605c53af6013c0ae7bc2aa3a490ba23f9238d69
The text was updated successfully, but these errors were encountered: