test: add logging in case of infinite loop

test-inspector-contexts may be entering an infinite loop (or very
long-running loop) in CI, resulting in flakiness. Or maybe not. Add
logging to find out.

PR-URL: #30649
Reviewed-By: Gireesh Punathil <[email protected]>
Reviewed-By: Anto Aravinth <[email protected]>
Reviewed-By: Denys Otrishko <[email protected]>
Reviewed-By: Luigi Pinca <[email protected]>

test/sequential/test-inspector-contexts.js

@@ -65,8 +65,10 @@ async function testContextCreatedAndDestroyed() {
                        JSON.stringify(contextCreated));
 
     // GC is unpredictable...
+    console.log('Checking/waiting for GC.');
     while (!contextDestroyed)
       global.gc();
+    console.log('Context destroyed.');
 
     assert.strictEqual(contextDestroyed.params.executionContextId, id,
                        JSON.stringify(contextDestroyed));
@@ -95,8 +97,10 @@ async function testContextCreatedAndDestroyed() {
                        JSON.stringify(contextCreated));
 
     // GC is unpredictable...
+    console.log('Checking/waiting for GC again.');
     while (!contextDestroyed)
       global.gc();
+    console.log('Other context destroyed.');
   }
 
   {
@@ -119,8 +123,10 @@ async function testContextCreatedAndDestroyed() {
                        JSON.stringify(contextCreated));
 
     // GC is unpredictable...
+    console.log('Checking/waiting for GC a third time.');
     while (!contextDestroyed)
       global.gc();
+    console.log('Context destroyed once again.');
   }
 
   {
@@ -141,8 +147,10 @@ async function testContextCreatedAndDestroyed() {
                        JSON.stringify(contextCreated));
 
     // GC is unpredictable...
+    console.log('Checking/waiting for GC a fourth time.');
     while (!contextDestroyed)
       global.gc();
+    console.log('Context destroyed a fourth time.');
   }
 }