You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe
As of now, build and integration test failures are notified via GitHub issue based on CI failures.
There are few issues with this:
Its completely string based. For build failure, it searches for Error building ... string and creates issues for those components. Similarly for integration tests, it follows exit codes.
Even if the failure is due to CI glitch (agent nodes not coming up or windows being glicthy usually) it treats it as a component failure and creates the GH issue.
Integration test failure issues are not closed automatically. This was by design as the workflow runs are run separately for each distribution, platform and architecture. An enhancement to detect no labels and close the issue was not executed. [Bug]: Auto close the created AUTOCUT integration test failure issues. #4495
Describe the solution you'd like
We are indexing all the build, test and release data in opensearch-metrics cluster.
Use this data as the source of truth to create, update and close the GH issues rather than depending on the string and CI failures.
Describe alternatives you've considered
No response
Additional context
The scope of this issue is to refactor notification only. For flaky tests detection see #4171
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe
As of now, build and integration test failures are notified via GitHub issue based on CI failures.
There are few issues with this:
Error building ...
string and creates issues for those components. Similarly for integration tests, it follows exit codes.Describe the solution you'd like
We are indexing all the build, test and release data in opensearch-metrics cluster.
Use this data as the source of truth to create, update and close the GH issues rather than depending on the string and CI failures.
Describe alternatives you've considered
No response
Additional context
The scope of this issue is to refactor notification only. For flaky tests detection see #4171
The text was updated successfully, but these errors were encountered: