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.

Sign up for GitHub

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

Jump to bottom

net: add some more practical tests for TCP keep-alive mechanism #65834

Open
panjf2000 opened this issue Feb 21, 2024 · 0 comments
Open

net: add some more practical tests for TCP keep-alive mechanism #65834

panjf2000 opened this issue Feb 21, 2024 · 0 comments
Assignees
@panjf2000
Labels
help wanted NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one. Testing An issue that has been verified to require only test changes, not just a test failure.
Milestone
Backlog

Comments

@panjf2000
Copy link
Member

This is a tracking issue of testing the TCP keep-alive mechanism in Go.

The current test suites are based on this previous discussion. They were good enough back then, but they might miss something like #65809, which directs us here, to investigate the possibility of introducing some additional tests that will reflect the real world.

CC @bcmills @ianlancetaylor @neild
@panjf2000 panjf2000 added help wanted NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one. labels Feb 21, 2024
@panjf2000 panjf2000 self-assigned this Feb 21, 2024
@bcmills bcmills added the Testing An issue that has been verified to require only test changes, not just a test failure. label Feb 21, 2024
@bcmills bcmills added this to the Backlog milestone Feb 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@panjf2000 panjf2000

Labels
help wanted NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one. Testing An issue that has been verified to require only test changes, not just a test failure.
Projects
None yet
Milestone
Backlog
Development

No branches or pull requests
2 participants
@bcmills @panjf2000