From 8345a60d3a642d3b27cd436f1c433e67deb1e29c Mon Sep 17 00:00:00 2001
From: Stephen Belanger <stephen.belanger@datadoghq.com>
Date: Sun, 8 Sep 2024 07:21:18 -0700
Subject: [PATCH] test: fix Windows async-context-frame memory failure

PR-URL: https://github.com/nodejs/node/pull/54823
Reviewed-By: James M Snell <jasnell@gmail.com>
Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
Reviewed-By: Jake Yuesong Li <jake.yuesong@gmail.com>
Reviewed-By: Rafael Gonzaga <rafael.nunu@hotmail.com>
---
 test/parallel/test-async-context-frame.mjs | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/test/parallel/test-async-context-frame.mjs b/test/parallel/test-async-context-frame.mjs
index cad5d07bbd17cd..87f0792702f9d5 100644
--- a/test/parallel/test-async-context-frame.mjs
+++ b/test/parallel/test-async-context-frame.mjs
@@ -42,7 +42,8 @@ const tests = testSets.reduce((m, v) => {
 }, []);
 
 describe('AsyncContextFrame', {
-  concurrency: tests.length
+  // TODO(qard): I think high concurrency causes memory problems on Windows
+  // concurrency: tests.length
 }, () => {
   for (const test of tests) {
     it(test, async () => {