nodejs
diff --git a/Collapse file
‎test/common/README.md‎
Copy file name to clipboardExpand all lines: test/common/README.md
+2-3Lines changed: 2 additions & 3 deletions
Display the source diff
Display the rich diff b/Collapse file
‎test/common/README.md‎
Copy file name to clipboardExpand all lines: test/common/README.md
+2-3Lines changed: 2 additions & 3 deletions
Display the source diff
Display the rich diff
diff --git a/Collapse file
‎test/common/cpu-prof.js‎
Copy file name to clipboardExpand all lines: test/common/cpu-prof.js
+1-12Lines changed: 1 addition & 12 deletions b/Collapse file
‎test/common/cpu-prof.js‎
Copy file name to clipboardExpand all lines: test/common/cpu-prof.js
+1-12Lines changed: 1 addition & 12 deletions
diff --git a/Collapse file
‎test/fixtures/workload/fibonacci.js‎
Copy file name to clipboardExpand all lines: test/fixtures/workload/fibonacci.js
+8-1Lines changed: 8 additions & 1 deletion b/Collapse file
‎test/fixtures/workload/fibonacci.js‎
Copy file name to clipboardExpand all lines: test/fixtures/workload/fibonacci.js
+8-1Lines changed: 8 additions & 1 deletion
@@ -438,10 +438,9 @@ The `cpu-prof` module provides utilities related to CPU profiling tests.
 
 ### env
 
-* Default: { ...process.env, FIB, NODE_DEBUG_NATIVE: 'INSPECTOR_PROFILER' }
+* Default: { ...process.env, NODE_DEBUG_NATIVE: 'INSPECTOR_PROFILER' }
 
-Environment variables used in profiled processes. FIB will be set to `40` on
-Windows and `30` elsewhere.
+Environment variables used in profiled processes.
 
 ### getCpuProfiles(dir)
 
 
@@ -2,7 +2,7 @@
 
 'use strict';
 
-const common = require('./');
+require('./');
 const fs = require('fs');
 const path = require('path');
 const assert = require('assert');
@@ -34,23 +34,12 @@ function verifyFrames(output, file, suffix) {
   assert.notDeepStrictEqual(frames, []);
 }
 
-let FIB = 30;
-// This is based on emperial values - in the CI, on Windows the program
-// tend to finish too fast then we won't be able to see the profiled script
-// in the samples, so we need to bump the values a bit. On slower platforms
-// like the Pis it could take more time to complete, we need to use a
-// smaller value so the test would not time out.
-if (common.isWindows) {
-  FIB = 40;
-}
-
 // We need to set --cpu-interval to a smaller value to make sure we can
 // find our workload in the samples. 50us should be a small enough sampling
 // interval for this.
 const kCpuProfInterval = 50;
 const env = {
   ...process.env,
-  FIB,
   NODE_DEBUG_NATIVE: 'INSPECTOR_PROFILER'
 };
 
 
@@ -4,5 +4,12 @@ function fib(n) {
   return fib(n - 1) + fib(n - 2);
 }
 
-const n = parseInt(process.env.FIB) || 35;
+// This is based on emperial values - in the CI, on Windows the program
+// tend to finish too fast then we won't be able to see the profiled script
+// in the samples, so we need to bump the values a bit. On slower platforms
+// like the Pis it could take more time to complete, we need to use a
+// smaller value so the test would not time out.
+const FIB = process.platform === 'win32' ? 40 : 30;
+
+const n = parseInt(process.env.FIB) || FIB;
 process.stdout.write(`${fib(n)}\n`);