-
Notifications
You must be signed in to change notification settings - Fork 3.5k
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
remove irrelevant warning for internal pipeline #16938
remove irrelevant warning for internal pipeline #16938
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM once CI is green
Quality Gate passedIssues Measures |
💚 Build Succeeded
History
|
@logstashmachine backport 8.x |
@logstashmachine backport 8.17 |
@logstashmachine backport 8.16 |
This commit removed irrelevant warning for internal pipeline, such as monitoring pipeline. Monitoring pipeline is expected to be one worker. The warning is not useful Fixes: #13298 (cherry picked from commit 3f41828) Co-authored-by: kaisecheng <[email protected]>
This commit removed irrelevant warning for internal pipeline, such as monitoring pipeline. Monitoring pipeline is expected to be one worker. The warning is not useful Fixes: #13298 (cherry picked from commit 3f41828) Co-authored-by: kaisecheng <[email protected]>
This commit removed irrelevant warning for internal pipeline, such as monitoring pipeline. Monitoring pipeline is expected to be one worker. The warning is not useful Fixes: #13298 (cherry picked from commit 3f41828) Co-authored-by: kaisecheng <[email protected]>
This commit removed irrelevant warning for internal pipeline, such as monitoring pipeline.
Monitoring pipeline is expected to be one worker. The warning is not useful
Fixes: #13298