-
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
Mute DLQ test on Windows #15843
Mute DLQ test on Windows #15843
Conversation
This commit mutes the DLQ test: `testDLQWriterFlusherRemovesExpiredSegmentWhenCurrentHeadSegmentIsEmpty` when running on Windows. Closes elastic#15768
Quality Gate passedKudos, no new issues were introduced! 0 New issues |
💚 Build Succeeded
cc @dliappis |
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
Fix request already tracked by #15767
@logstashmachine backport 8.12 |
As discussed in #15768 (comment), this test existed only in |
This commit mutes the DLQ test: `testDLQWriterFlusherRemovesExpiredSegmentWhenCurrentHeadSegmentIsEmpty` when running on Windows. Closes #15768 (cherry picked from commit c33afd4) Co-authored-by: Dimitrios Liappis <[email protected]>
Release notes
[rn:skip]
What does this PR do?
This commit mutes the DLQ test:
testDLQWriterFlusherRemovesExpiredSegmentWhenCurrentHeadSegmentIsEmpty
when running on Windows.How to test this PR locally
Using this PR:
Example windows build: https://buildkite.com/elastic/logstash-windows-jdk-matrix-pipeline/builds/82#_
Example Linux build: https://buildkite.com/elastic/logstash-pull-request-pipeline/builds/754#018d376b-b614-4fa2-9a63-d8433bcc1207
Related issues
testDLQWriterFlusherRemovesExpiredSegmentWhenCurrentHeadSegmentIsEmpty
on WIndows #15768