From abc2ff47c211ae2da12d64dde2257faae6644121 Mon Sep 17 00:00:00 2001
From: James M Snell <jasnell@gmail.com>
Date: Tue, 12 Jan 2021 11:29:13 -0800
Subject: [PATCH] test: disable test-crypto-secure-heap with asan

The asan checks don't play well currently with persistent secure
heap allocations.

Signed-off-by: James M Snell <jasnell@gmail.com>

PR-URL: https://github.com/nodejs/node/pull/36900
Refs: https://github.com/nodejs/node/pull/36881
Reviewed-By: Danielle Adams <adamzdanielle@gmail.com>
Reviewed-By: Richard Lau <rlau@redhat.com>
Reviewed-By: Antoine du Hamel <duhamelantoine1995@gmail.com>
Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
Reviewed-By: Filip Skokan <panva.ip@gmail.com>
---
 test/parallel/test-crypto-secure-heap.js | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/test/parallel/test-crypto-secure-heap.js b/test/parallel/test-crypto-secure-heap.js
index 2a851019b5eb84..f6bdc3a2d8a05c 100644
--- a/test/parallel/test-crypto-secure-heap.js
+++ b/test/parallel/test-crypto-secure-heap.js
@@ -7,6 +7,9 @@ if (!common.hasCrypto)
 if (common.isWindows)
   common.skip('Not supported on Windows');
 
+if (process.config.variables.asan)
+  common.skip('ASAN does not play well with secure heap allocations');
+
 const assert = require('assert');
 const { fork } = require('child_process');
 const fixtures = require('../common/fixtures');