test: move test-shadow-realm-gc.js to known_issues

There is actually a leak. The test doesn't exercise the right path to create a substantial enough object graph (e.g. accessing something that results in the loading of a binding). This does something more complicated in the test and moves it to known_issues until we find a fix.
nodejs · nodejs-github-bot · Apr 4, 2023 · Apr 1, 2023 · Apr 3, 2023 · Apr 3, 2023
commit 4e89ddbda5296dd6e206ead26d37f7a578998550
diff --git a/test/parallel/test-shadow-realm-gc.js → test/known_issues/test-shadow-realm-gc.js b/test/parallel/test-shadow-realm-gc.js → test/known_issues/test-shadow-realm-gc.js
@@ -8,5 +8,6 @@
 require('../common');
 
 for (let i = 0; i < 1000; i++) {
-  new ShadowRealm();
+  const realm = new ShadowRealm();
+  realm.evaluate(`new TextEncoder(); 1;`);
 }