Uh oh!
There was an error while loading. Please reload this page.
test: replace port in dgram cb test - #12942
Conversation
Trott
commented
May 10, 2017
It would be great if your commit messages and PR titles could be less generic. Having multiple PRs with identical titles makes it really hard to track what's going on. Including the test name would be helpful. |
You got it, will change the commit messages and name of the PRs. Thanks |
arturgvieira-zz
commented
May 10, 2017
@Trott updated the PR titles and commit message headings. Let me know your thoughts. |
Trott
commented
May 10, 2017
Thanks. That's much easier to differentiate in notifications. |
arturgvieira-zz
commented
May 10, 2017
Thank you. I am still new and appreciate learning best practices. Thanks for taking the time to explain. |
There was a problem hiding this comment.
You could just use the existing client socket here.
cjihrig
commented
May 11, 2017
Call |
Oh, I see, thanks for the help. |
lpinca
commented
May 11, 2017
For anyone reviewing, see discussion in #12929. |
There was a problem hiding this comment.
This line is too long, the linter will not like it.
arturgvieira-zz
commented
May 12, 2017
@lpinca All done, wrapped arguments to shorten line length. |
There was a problem hiding this comment.
Has this new test been added by mistake?
There was a problem hiding this comment.
Yes, I'm sorry my mistake, give me a second and I will correct that.
Replaced common.PORT in the following test. test-dgram-send-callback-buffer.js Ref: #12376
lpinca
commented
May 22, 2017
Landed in e00116d. |
Replaced common.PORT in the following test.
test-dgram-send-callback-buffer.js
Ref: #12376
Checklist
make -j4 test(UNIX), orvcbuild test(Windows) passesAffected core subsystem(s)
test dgram