test: fix flaky test-crypto-timing-safe-dqual-benchmarks

Fixes: #38226

PR-URL: #38476
Reviewed-By: Antoine du Hamel <[email protected]>
Reviewed-By: Ruy Adorno <[email protected]>
Reviewed-By: James M Snell <[email protected]>

Author: Trott

lib/internal/bootstrap/node.js

@@ -46,7 +46,6 @@ const {
   ObjectGetPrototypeOf,
   ObjectPreventExtensions,
   ObjectSetPrototypeOf,
-  Proxy,
   ReflectGet,
   ReflectSet,
   SymbolToStringTag,
@@ -108,8 +107,10 @@ const deprecationHandler = {
 
   get(target, key, receiver) {
     const val = ReflectGet(target, key, receiver);
-    if (val != null && typeof val === 'object')
+    if (val != null && typeof val === 'object') {
+      // eslint-disable-next-line node-core/prefer-primordials
       return new Proxy(val, deprecationHandler);
+    }
     return val;
   },
 
@@ -119,6 +120,7 @@ const deprecationHandler = {
   }
 };
 
+// eslint-disable-next-line node-core/prefer-primordials
 let processConfig = new Proxy(
   JSONParse(nativeModule.config),
   deprecationHandler);

test/pummel/test-crypto-timing-safe-equal-benchmarks.js

@@ -111,7 +111,7 @@ assert(
   `timingSafeEqual should not leak information from its execution time (t=${t})`
 );
 
-// As a sanity check to make sure the statistical tests are working, run the
+// As a coherence check to make sure the statistical tests are working, run the
 // same benchmarks again, this time with an unsafe comparison function. In this
 // case the t-value should be above the threshold.
 const unsafeCompare = (bufA, bufB) => bufA.equals(bufB);