1berry/nodejs
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

test: fix test-http-pipeline-flood

Browse Source 
The number of connections achieved by the test can vary by platform
and by machine. Lowering the acceptance threshold so that the
test passes on Windows.
This commit is contained in:
Alexis Campailla 2014-02-06 05:43:55 -08:00 committed by Fedor Indutny
parent eadb4f5606
commit e3ec2f7dab
1 changed files with 5 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
test/simple/test-http-pipeline-flood.js
View File

@ -71,12 +71,11 @@ function parent() {
assert(gotTimeout); assert(gotTimeout);
assert(childClosed); assert(childClosed);
assert.equal(connections, 1); assert.equal(connections, 1);
// 1213 works out to be the number of requests we end up processing // The number of requests we end up processing before the outgoing
// before the outgoing connection backs up and requires a drain. // connection backs up and requires a drain is implementation-dependent.
// however, to avoid being unnecessarily tied to a specific magic number, // We can safely assume is more than 250.
// and making the test brittle, just assert that it's "a lot", which we console.log('server got %d requests', requests);
// can safely assume is more than 500. assert(requests >= 250);
assert(requests >= 500);
console.log('ok'); console.log('ok');
}); });
} }