test: skip tests that cause timeouts on IBM i

[abmusse]

I missed marking a couple of test cases flaky in my previous PR:
#58583

tests missed were:

• parallel.test-inspector-network-content-type
• benchmark.test-benchmark-websocket

After marking the above flaky I re-ran a test build and noticed
the build still failed.

Unfortuantely the build still fails because the build detects that
node process are left behind after the tests, presumably because tests
that spawn child processes are being timed out and only the parent
process is killed off, leaving the child processes behind.

see: #59014 (comment)

We've decided to skip these tests until the underlying issue is
resolved.

The tests being skipped are:

• parallel.test-http-proxy-fetch
• parallel.test-https-proxy-fetch
• benchmark.test-benchmark-websocket
• parallel.test-inspector-network-fetch
• parallel.test-inspector-network-content-type
• es-module.test-wasm-web-api
• parallel.test-fetch
• parallel.test-without-async-context-frame
• report.test-report-exclude-network

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 90.08%. Comparing base (09b4c57) to head (db5c570).
Report is 6 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff            @@
##             main   #59014    +/-   ##
========================================
  Coverage   90.07%   90.08%            
========================================
  Files         641      645     +4     
  Lines      188998   189128   +130     
  Branches    37069    37094    +25     
========================================
+ Hits       170246   170370   +124     
- Misses      11462    11464     +2     
- Partials     7290     7294     +4     

see 44 files with indirect coverage changes

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[richardlau]

Test build: https://ci.nodejs.org/job/node-test-commit-ibmi/nodes=ibmi74-ppc64/2003/console

So unfortunately the build still fails because the build detects that node process are left behind after the tests, presumably because tests that spawn child processes are being timed out and only the parent process is killed off, leaving the child processes behind:

05:57:54 All tests passed.
05:57:54 "/home/IOJS/build/workspace/node-test-commit-ibmi/nodes/ibmi74-ppc64/node" ./test/embedding/test-embedding.js
05:58:14 ps awwx | grep Release/node | grep -v grep | cat
05:58:14  5257763      - A    28:20 /home/IOJS/build/workspace/node-test-commit-ibmi/nodes/ibmi74-ppc64/out/Release/node /home/IOJS/build/workspace/node-test-commit-ibmi/nodes/ibmi74-ppc64/test/fixtures/fetch-and-log.mjs 
05:58:14  5258203      - A    27:59 /home/IOJS/build/workspace/node-test-commit-ibmi/nodes/ibmi74-ppc64/out/Release/node /home/IOJS/build/workspace/node-test-commit-ibmi/nodes/ibmi74-ppc64/test/fixtures/fetch-and-log.mjs 
05:58:14  5265655      - A     0:00 /home/IOJS/build/workspace/node-test-commit-ibmi/nodes/ibmi74-ppc64/out/Release/node --test-reporter=./test/common/test-error-reporter.js --test-reporter-destination=stdout /home/IOJS/build/workspace/node-test-commit-ibmi/nodes/ibmi74-ppc64/benchmark/run.js test websocket 
05:58:14  5265656      - A     0:00 /home/IOJS/build/workspace/node-test-commit-ibmi/nodes/ibmi74-ppc64/out/Release/node --test-reporter=./test/common/test-error-reporter.js --test-reporter-destination=stdout /home/IOJS/build/workspace/node-test-commit-ibmi/nodes/ibmi74-ppc64/benchmark/websocket/simple.js --test 
05:58:14  5265660      - A    13:38 /home/IOJS/build/workspace/node-test-commit-ibmi/nodes/ibmi74-ppc64/out/Release/node --test-reporter=./test/common/test-error-reporter.js --test-reporter-destination=stdout /home/IOJS/build/workspace/node-test-commit-ibmi/nodes/ibmi74-ppc64/benchmark/websocket/simple.js roundtrips=1 useBinary=true size=1 
05:58:14 gmake[1]: *** [Makefile:609: test-ci] Error 1

[abmusse]

So unfortunately the build still fails because the build detects that node process are left behind after the tests, presumably because tests that spawn child processes are being timed out and only the parent process is killed off, leaving the child processes behind

Thanks for pointing that out. Since that behavior is happening do you think we should skip the tests (until we resolve the underlying issue) so that they don't spawn the child processes?

[richardlau]

So unfortunately the build still fails because the build detects that node process are left behind after the tests, presumably because tests that spawn child processes are being timed out and only the parent process is killed off, leaving the child processes behind

Thanks for pointing that out. Since that behavior is happening do you think we should skip the tests (until we resolve the underlying issue) so that they don't spawn the child processes?

Yes, let's go with skipping until we figure out why they're timing out.

[abmusse]

Updated test build: https://ci.nodejs.org/job/node-test-commit-ibmi/nodes=ibmi74-ppc64/2005/console

[nodejs-github-bot]

CI: https://ci.nodejs.org/job/node-test-pull-request/67927/

[mhdawson]

LGTM