grpc-go
grpc-go copied to clipboard
test/keepalive: Improve TestKeepaliveClientClosesWithActiveStreams
Setup a ping/noping switchable server to use in KeepaliveClientClosesWithActiveStreams test
Fixes #6099
RELEASE NOTES: N/A
@arvindbr8 Hello, I'm unsure about what caused Testing / vet-proto (pull_request) above to fail and how to fix it for this PR. Is it something you could help me with? Thanks in advance.
Hello, I'm unsure about what caused Testing / vet-proto (pull_request) above to fail
This one is not actionable in your PR. And I believe extras should be fixed if you fetch master@HEAD and rebase+force-push (or merge into?) your branch.
Thanks @dfawley It helped. However, are Test/DialWaitsForServerSettingsAndFails and Test/FullHandshake known flaky? They failed in the last run (one in Testing / tests (tests, 1.20) (pull_request) and the other in Testing / tests (tests, 1.20, arm64) (pull_request) ), but they are not related to the fix I pushed. Any thoughts?
Hey @tobotg Test/DialWaitsForServerSettingsAndFails and Test/FullHandshake are not known flakes. I've triggered a re-run. lets see how that goes.
Hey @arvindbr8 all the tests passed now, so it's. btw, thanks for the review. I'll look into it and get back here.
This PR is labeled as requiring an update from the reporter, and no update has been received after 6 days. If no update is provided in the next 7 days, this issue will be automatically closed.
I've been very busy lately, hopefully I'll be able to get back to this during the weekend.
Hey @arvindbr8 , I gave it another try. Please have a look when you get a chance. Thanks
@arvindbr8 is out of town for a couple weeks; will resume when he returns.
Hey @tobotg, thanks for the revision. I will take a look at it shortly.
thanks @tobotg, Changes looks better now. A few minor comments and nits. Please take a look and let us know.
Thanks @arvindbr8 for the review. I had a look and addressed the changes you requested. Please let me know how it looks now.
@tobotg, Please let us know when you want us to take another look at this.
@arvindbr8 Thanks for the review (and I added your comment). Please take another look when you get a chance.
@arvindbr8 All passed now. @dfawley
This PR is labeled as requiring an update from the reporter, and no update has been received after 6 days. If no update is provided in the next 7 days, this issue will be automatically closed.
@dfawley hopefully I'll be able to get back to this during the weekend and address your comments. Thanks
This PR is labeled as requiring an update from the reporter, and no update has been received after 6 days. If no update is provided in the next 7 days, this issue will be automatically closed.
Back to it. I'll submit a new commit this week. Thanks
This PR is labeled as requiring an update from the reporter, and no update has been received after 6 days. If no update is provided in the next 7 days, this issue will be automatically closed.
I made changes, and I'll submit later after tests. Thanks
@dfawley Hello! I just submitted a new commit now, I hope it captured the feedback you shared recently. However, I'm unsure what the vet issue is here, any clue will be appreciated.Thanks
If you rebase your branch to master, the vet issue should get fixed. Either way, it does not affect the ability to merge the changes once approved.
If you rebase your branch to master
In general, it's best to not rebase a PR from master until the reviews are done, as it messes up github diffs and review comment threads.
In this particular case, it's not necessary at all, because the vet-proto checker is optional and the failure is because external/unrelated things are out of sync that we will fix separately.
Hello @dfawley and @arvindbr8 Just in case I missed it, I wanted to check in if there is any clarification or task needed from me on this PR before review. Thanks
This PR is labeled as requiring an update from the reporter, and no update has been received after 6 days. If no update is provided in the next 7 days, this issue will be automatically closed.
Thanks @arvindbr8 for the review. I'll look into it during this weekend and get back to you if more elaboration needed.
This PR is labeled as requiring an update from the reporter, and no update has been received after 6 days. If no update is provided in the next 7 days, this issue will be automatically closed.