-
Notifications
You must be signed in to change notification settings - Fork 116
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
[tcp-close] New whocloses semantics #630
Conversation
@anandbonde could you change the description of this issue so that it links issues correctly? https://docs.github.com/en/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue |
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.
Tests are not passing. Why? Could you file an issue to keep track of this bug? If you disable this test for some LibOSes, could you file an issue to keep track which LibOSes fall in this condition?
61455b7
to
5faee03
Compare
Done |
5faee03
to
8711b5a
Compare
I just checked the logs, the tests are failing because I have added a new argument to the tcp-close utility, but the ci scripts are not updated to use it. I think it would be good to change the ci scripts to be updated in this PR itself so that we don't have to revisit this area. Do you have any preference? |
Please, update the CI scripts accordingly. I am also confident that this will not work for all LibOSes (it should expose bugs). For those LibOSes which the CI does not pass, disable them and file an issue to keep track of. |
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
8711b5a
to
6ac6b2f
Compare
6ac6b2f
to
e5bfc8c
Compare
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 the issue on remove()
is fixed.
Closes #526