mirror of
https://github.com/nodejs/node.git
synced 2024-12-01 16:10:02 +01:00
e9ba0cfd46
Currently when building --without-ssl a 'ERR_NO_CRYPTO' error is reported. This is not currently being picked up by the crypto-check lint rule as it does not actually require any crypto modules directly, but instead this is done by common/benchmark. PR-URL: https://github.com/nodejs/node/pull/18724 Reviewed-By: Ruben Bridgewater <ruben@bridgewater.de> Reviewed-By: Benjamin Gruenbaum <benjamingr@gmail.com> Reviewed-By: Richard Lau <riclau@uk.ibm.com> Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: Tobias Nießen <tniessen@tnie.de> Reviewed-By: Luigi Pinca <luigipinca@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com>
29 lines
732 B
JavaScript
29 lines
732 B
JavaScript
'use strict';
|
|
|
|
const common = require('../common');
|
|
|
|
if (!common.hasCrypto)
|
|
common.skip('missing crypto');
|
|
|
|
if (!common.enoughTestMem)
|
|
common.skip('Insufficient memory for TLS benchmark test');
|
|
|
|
// Because the TLS 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.
|
|
|
|
const runBenchmark = require('../common/benchmark');
|
|
|
|
runBenchmark('tls',
|
|
[
|
|
'concurrency=1',
|
|
'dur=0.1',
|
|
'n=1',
|
|
'size=2',
|
|
'type=asc'
|
|
],
|
|
{
|
|
NODEJS_BENCHMARK_ZERO_ALLOWED: 1,
|
|
duration: 0
|
|
});
|