-
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
Ignore test testDLQWriterFlusherRemovesExpiredSegmentWhenCurrentHeadSegmentIsEmpty
on WIndows
#15768
Comments
In case it could be a useful data point, wanted to share that we don't observe Windows failures with the |
dliappis
added a commit
to dliappis/logstash
that referenced
this issue
Jan 23, 2024
This commit mutes the DLQ test: `testDLQWriterFlusherRemovesExpiredSegmentWhenCurrentHeadSegmentIsEmpty` when running on Windows. Closes elastic#15768
dliappis
added a commit
that referenced
this issue
Jan 24, 2024
This commit mutes the DLQ test: `testDLQWriterFlusherRemovesExpiredSegmentWhenCurrentHeadSegmentIsEmpty` when running on Windows. Closes #15768
dliappis
added a commit
that referenced
this issue
Jan 24, 2024
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]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Given that the test
DeadLetterQueueWriterAgeRetentionTest .testDLQWriterFlusherRemovesExpiredSegmentWhenCurrentHeadSegmentIsEmpty
fails only on Windows platform, ignore selectively the test for that environment.For example, with JUnit4 we could leverage the
Assume
and at the start of the test:The text was updated successfully, but these errors were encountered: