test: add logging to test-worker-memory

To help troubleshoot CI failures, add some logging. Refs: #23277 (comment) PR-URL: #23418 Reviewed-By: Anna Henningsen <[email protected]> Reviewed-By: Gireesh Punathil <[email protected]> Reviewed-By: Sakthipriyan Vairamani <[email protected]>
nodejs · Oct 30, 2018 · 27dd4de · 27dd4de
1 parent ffadcc1
commit 27dd4de
Showing 1 changed file with 2 additions and 0 deletions.
diff --git a/test/parallel/test-worker-memory.js b/test/parallel/test-worker-memory.js
@@ -10,6 +10,7 @@ const numWorkers = +process.env.JOBS || require('os').cpus().length;
 // Verify that a Worker's memory isn't kept in memory after the thread finishes.
 
 function run(n, done) {
+  console.log(`run() called with n=${n} (numWorkers=${numWorkers})`);
   if (n <= 0)
     return done();
   const worker = new Worker(
@@ -27,6 +28,7 @@ const startStats = process.memoryUsage();
 let finished = 0;
 for (let i = 0; i < numWorkers; ++i) {
   run(60 / numWorkers, () => {
+    console.log(`done() called (finished=${finished})`);
     if (++finished === numWorkers) {
       const finishStats = process.memoryUsage();
       // A typical value for this ratio would be ~1.15.