remove unnecessary console debugging output

Author: IlyasShabi

test/pummel/test-heap-profile-and-snapshot-near-heap-limit.js

@@ -20,9 +20,7 @@ const child = spawnSync(process.execPath, [
   cwd: tmpdir.path,
 });
 
-console.log(child.stdout.toString());
 const stderr = child.stderr.toString();
-console.log(stderr);
 assert(common.nodeProcessAborted(child.status, child.signal),
        'process should have aborted, but did not');
 

test/pummel/test-heap-profile-near-heap-limit-with-heap-prof.js

@@ -23,8 +23,6 @@ const child = spawnSync(process.execPath, [
   cwd: tmpdir.path,
 });
 
-console.log(child.stdout.toString());
-console.log(child.stderr.toString());
 assert(common.nodeProcessAborted(child.status, child.signal),
        'process should have aborted, but did not');
 

test/pummel/test-heap-profile-near-heap-limit.js

@@ -20,8 +20,6 @@ const child = spawnSync(process.execPath, [
   cwd: tmpdir.path,
 });
 
-console.log(child.stdout.toString());
-console.log(child.stderr.toString());
 assert(common.nodeProcessAborted(child.status, child.signal),
        'process should have aborted, but did not');