-
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]: Opensearch build workflow flaky, creating multiple issues on Plugin repos #4141
Comments
Hi @monusingh-1 The builds are not flaky but the way GH create issue is written is buggy. As per my analysis this is the culprit: https://github.com/opensearch-project/opensearch-build/blob/main/manifests/3.0.0/opensearch-3.0.0.yml#L9 Looks like our infra is building on different java versions for linux and windows.
@peterzhuamazon created a PR to fix these recently. However, the failures are right. The error mentioned by you is java incompatible error (have seen that before). |
I think the above PR fixes the false positive. 3.0.0 is building right now https://build.ci.opensearch.org/blue/organizations/jenkins/distribution-build-opensearch/detail/distribution-build-opensearch/8677/pipeline/75 and I can see geospatial plugin failing on windows similar to linux (it was not happening before).
Will create an issue to fix the GH creation logic. |
Created issue to add more details to GH issue #4155 |
Describe the bug
When OS builds are triggered the workflow fails intermittently and cuts issue on plugin repos, the issues are then resolved in next run. When the next run happens a new issue is created.
129 issues have been cut so far https://github.com/opensearch-project/cross-cluster-replication/issues?q=is%3Aissue++%5BAUTOCUT%5D+Distribution+Build+Failed+for+cross-cluster-replication-3.0.0+
https://build.ci.opensearch.org/job/distribution-build-opensearch/8674/consoleFull
On CCR
on K-nn
Could you please confirm if the issues are actionable by plugin maintainers ?
How can we address the falky nature of this build ?
To reproduce
Expected behavior
No response
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: