Uh oh!
There was an error while loading. Please reload this page.
test: don't check the # of chunks in test-http-1.0 - #3961
Conversation
As it can happen that the HTTP response is received in more than one TCP chunk.
bnoordhuis
commented
Nov 23, 2015
I've never seen that test fail on OS X. What does the second chunk contain? |
santigimeno
commented
Nov 24, 2015
@bnoordhuis It only happened once so I can't really say. I could reproduce it later on increasing the size of the response but that's not the same test. I'll run the tests some more time during the following days and come back with the results |
santigimeno
commented
Nov 25, 2015
@bnoordhuis finally I could reproduce it. The second chunk: |
bnoordhuis
commented
Nov 25, 2015
Huh, thanks. I figured out why it happens. There are a couple of places where the test does this: res.write('Hello, ');res._send('');res.write('world!');res._send('');Which results in this: But ends up getting read as a single packet, most of the time anyway. I wonder if this isn't a performance issue (albeit a minor one) that we can fix by trying harder to coalesce writes. /cc @indutny - I know you were looking into a similar issue recently. Back to this PR, LGTM. CI: https://ci.nodejs.org/job/node-test-pull-request/851/ |
indutny
commented
Nov 25, 2015
Nah, this is not that much related to it. I think. |
indutny
commented
Nov 25, 2015
LGTM |
1 similar comment
JungMinu
commented
Dec 6, 2015
LGTM |
As it can happen that the HTTP response is received in more than one TCP chunk. PR-URL: #3961 Reviewed-By: Ben Noordhuis <info@bnoordhuis.nl> Reviewed-By: Fedor Indutny <fedor@indutny.com> Reviewed-By: Minwoo Jung <jmwsoft@gmail.com>
bnoordhuis
commented
Dec 7, 2015
Landed in dde2012, thanks Santiago. |
As it can happen that the HTTP response is received in more than one TCP chunk. PR-URL: #3961 Reviewed-By: Ben Noordhuis <info@bnoordhuis.nl> Reviewed-By: Fedor Indutny <fedor@indutny.com> Reviewed-By: Minwoo Jung <jmwsoft@gmail.com>
As it can happen that the HTTP response is received in more than one TCP chunk. PR-URL: #3961 Reviewed-By: Ben Noordhuis <info@bnoordhuis.nl> Reviewed-By: Fedor Indutny <fedor@indutny.com> Reviewed-By: Minwoo Jung <jmwsoft@gmail.com>
As it can happen that the HTTP response is received in more than one TCP chunk. PR-URL: #3961 Reviewed-By: Ben Noordhuis <info@bnoordhuis.nl> Reviewed-By: Fedor Indutny <fedor@indutny.com> Reviewed-By: Minwoo Jung <jmwsoft@gmail.com>
As it can happen that the HTTP response is received in more than one TCP chunk. PR-URL: #3961 Reviewed-By: Ben Noordhuis <info@bnoordhuis.nl> Reviewed-By: Fedor Indutny <fedor@indutny.com> Reviewed-By: Minwoo Jung <jmwsoft@gmail.com>
As it can happen that the HTTP response is received in more than one TCP chunk. PR-URL: nodejs#3961 Reviewed-By: Ben Noordhuis <info@bnoordhuis.nl> Reviewed-By: Fedor Indutny <fedor@indutny.com> Reviewed-By: Minwoo Jung <jmwsoft@gmail.com>
As it can happen that the HTTP response is received in more than
one TCP chunk.
It tries to fix the following failure I got in a
OS XboxNot to sure if this is the correct fix as I don't really understand the reason to check the number of chunks in this test.