| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
Sorry, something went wrong.
|
Trying to fail on freeBSD: https://ci.nodejs.org/job/node-test-commit-freebsd/9006/ |
Sorry, something went wrong.
There was a problem hiding this comment.
This should be removed.
Sorry, something went wrong.
There was a problem hiding this comment.
Ack.
I just added it to try to check something.
That test is interacting with the test of this PR.
Sorry, something went wrong.
|
Another BSD CI:https://ci.nodejs.org/job/node-test-commit-freebsd/9007/ |
Sorry, something went wrong.
|
A stress test CI job is better for checking flakiness fixes. |
Sorry, something went wrong.
|
I need to test the interaction of two test: |
Sorry, something went wrong.
|
Try to fail on freeBSD: https://ci.nodejs.org/job/node-stress-single-test/nodes=freebsd10-64/ |
Sorry, something went wrong.
Sorry, something went wrong.
| const host = common.localhostIPv4; | ||
|
|
||
| function serverOnConnection(socket) { | ||
| console.error(`'connection' ${++serverConnections} emitted on server`); |
There was a problem hiding this comment.
if the console output is not necessary for the test, please remove them :-)
Sorry, something went wrong.
There was a problem hiding this comment.
They were very usefull for debugging. Gone now.
Sorry, something went wrong.
Sorry, something went wrong.
|
This needs a rebase and there are a couple linter errors. |
Sorry, something went wrong.
|
ping @nodejs/testing |
Sorry, something went wrong.
Sorry, something went wrong.
I may be missing something important here, but you can run a stress test on just those two tests with something like: -j 4 --repeat 100 test/parallel/test-net-connect-local-error.js test/parallel/test-net-connect-options-allowhalfopen.js |
Sorry, something went wrong.
|
I have to attend to something else right now but I'll try to make a point to look at this in the next 24 hours... |
Sorry, something went wrong.
|
Any chance we can get a more detailed commit message? |
Sorry, something went wrong.
|
Change seem good to me but might be useful to get @bnoordhuis, @indutny, @nodejs/streams to take a look. |
Sorry, something went wrong.
Yeah I didn't think about it at the time.
I think we solved this dis-harmony by moving test-net-connect-local-error.js to sequential. So what's left in this PR if just refactoring. AFAICT this was blocked because @jasnell asked to remove the logging, but I'm -0 on that since the order of events in the test is tricky. Eventually it was the log that made me wonder where the 7th connection is coming from if the clients are only making 6 🤔 Mismatched serverOnConnection function calls. Expected 6, actual 7.
at forAllClients (/Users/iojs/build/workspace/node-test-commit-osx/nodes/osx1010/test/parallel/test-net-connect-options-allowhalfopen.js:44:38)
...
No. 4 connection is closing server:
7 FIN received by server,
6 FIN received by client,
6 FIN sent by client,
7 FIN sent by server
Server has been closed:
7 FIN received by server,
6 FIN received by client,
6 FIN sent by client,
7 FIN sent by server
|
Sorry, something went wrong.
There was a problem hiding this comment.
LGTM
Sorry, something went wrong.
PR-URL: nodejs#13003 Fixes: nodejs#12951 Reviewed-By: Matteo Collina <matteo.collina@gmail.com>
|
Quick sanity of master: https://ci.nodejs.org/job/node-test-commit-linuxone/8705/ |
Sorry, something went wrong.
PR-URL: nodejs/node#13003 Fixes: nodejs/node#12951 Reviewed-By: Matteo Collina <matteo.collina@gmail.com>
| Back | FazBrowse Home | New Git URL |
Try to stabilize test/parallel/test-net-connect-options-allowhalfopen.js
Fixes: #12951
Test is stable but could use some loving.
Checklist
Affected core subsystem(s)
test,net