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

test: move benchmark-dgram to sequential

Browse Source 
This test uses hardcoded ports, it should not be located in parallel.

PR-URL: https://github.com/nodejs/node/pull/21144
Reviewed-By: Michaël Zasso <targos@protonmail.com>
Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
Reviewed-By: Joyee Cheung <joyeec9h3@gmail.com>
Reviewed-By: Trivikram Kamat <trivikr.dev@gmail.com>
Reviewed-By: Rich Trott <rtrott@gmail.com>
This commit is contained in:
Anatoli Papirovski 2018-06-04 15:08:16 +02:00 committed by Rich Trott
parent fc3fd60413
commit d0943bcb69
1 changed files with 4 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
test/parallel/test-benchmark-dgram.js → test/sequential/test-benchmark-dgram.js
View File

@ -4,6 +4,10 @@ require('../common');
const runBenchmark = require('../common/benchmark'); const runBenchmark = require('../common/benchmark');
// Because the dgram benchmarks use hardcoded ports, this should be in
// sequential rather than parallel to make sure it does not conflict with
// tests that choose random available ports.
runBenchmark('dgram', ['address=true', runBenchmark('dgram', ['address=true',
'chunks=2', 'chunks=2',
'dur=0.1', 'dur=0.1',