Skip to content
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

Enable SocketHalfClosedTest for epoll #13025

Merged
merged 2 commits into from Nov 29, 2022
Merged

Conversation

chrisvest
Copy link
Contributor

Motivation:
These tests were not being run for epoll because the classes did not have the Test suffix. We also aren't regularly running these tests for kqueue because we don't have a MacOS CI build. It turns out that all transports now behave consistently with regards to read-completes after input shutdown, so the tests don't need to change their assertions for epoll/kqueue vs. NIO.

Modification:
Enable the SocketHalfClosedTest for epoll, both edge and level triggered. Remove test parameter adjustments for epoll and kqueue.

Result:
SocketHalfClosedTest tests now run, and pass, for epoll.

This is a back port of #12993

Motivation:
These tests were not being run for epoll because the classes did not have the Test suffix.
We also aren't regularly running these tests for kqueue because we don't have a MacOS CI build.
It turns out that all transports now behave consistently with regards to read-completes after input shutdown, so the tests don't need to change their assertions for epoll/kqueue vs. NIO.

Modification:
Enable the SocketHalfClosedTest for epoll, both edge and level triggered.
Remove test parameter adjustments for epoll and kqueue.

Result:
SocketHalfClosedTest tests now run, and pass, for epoll.
Although, this really should not be part of the public API.
@normanmaurer normanmaurer added this to the 4.1.86.Final milestone Nov 29, 2022
@normanmaurer normanmaurer merged commit 1baf9ef into netty:4.1 Nov 29, 2022
@chrisvest chrisvest deleted the 41-half-close branch November 29, 2022 17:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants