From a735af2ecd9605305a22f36657eab464b3feedec Mon Sep 17 00:00:00 2001
From: Daniel Bevenius <daniel.bevenius@gmail.com>
Date: Mon, 12 Feb 2018 07:28:41 +0100
Subject: [PATCH] test: add crypto check to test-benchmark-tls
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

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>
---
 test/sequential/test-benchmark-tls.js | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/test/sequential/test-benchmark-tls.js b/test/sequential/test-benchmark-tls.js
index 7c87aa3cbcd89e..3545955e3ab5b0 100644
--- a/test/sequential/test-benchmark-tls.js
+++ b/test/sequential/test-benchmark-tls.js
@@ -2,6 +2,9 @@
 
 const common = require('../common');
 
+if (!common.hasCrypto)
+  common.skip('missing crypto');
+
 if (!common.enoughTestMem)
   common.skip('Insufficient memory for TLS benchmark test');