test: mark timeouts & flaky test as flaky on IBM i

Underlying issues still need to be investigated but this will prevent these failures from failing the daily builds. Timeouts: - parallel.test-http-proxy-fetch - parallel.test-https-proxy-fetch - benchmark.test-benchmark-websocket - parallel.test-inspector-network-fetch - es-module.test-wasm-web-api - parallel.test-fetch - parallel.test-without-async-context-frame - report.test-report-exclude-network Flaky test: - parallel.test-process-cpuUsage PR-URL: #58583 Refs: #58582 Reviewed-By: Joyee Cheung <joyeec9h3@gmail.com> Reviewed-By: Richard Lau <rlau@redhat.com> Reviewed-By: Luigi Pinca <luigipinca@gmail.com>

Author: abmusse

test/es-module/es-module.status

@@ -13,3 +13,7 @@ test-esm-loader-http-imports: PASS,FLAKY
 [$arch==arm || $arch==arm64]
 # https://github.com/nodejs/node/issues/47297
 test-wasm-web-api: SKIP
+
+[$system==ibmi]
+# https://github.com/nodejs/node/issues/58582
+test-wasm-web-api: PASS,FLAKY

test/parallel/parallel.status

@@ -123,6 +123,14 @@ test-tls-client-mindhsize: PASS, FLAKY
 test-tls-write-error: PASS, FLAKY
 # https://github.com/nodejs/node/issues/48047
 test-http-pipeline-flood: SKIP
+# https://github.com/nodejs/node/issues/58582
+test-http-proxy-fetch: PASS, FLAKY
+test-https-proxy-fetch: PASS, FLAKY
+test-inspector-network-fetch: PASS, FLAKY
+test-fetch: PASS, FLAKY
+test-without-async-context-frame: PASS, FLAKY
+test-process-cpuUsage: PASS, FLAKY
+
 
 [$asan==on]
 # https://github.com/nodejs/node/issues/39655

test/report/report.status

@@ -9,3 +9,7 @@ prefix report
 [$system==solaris] # Also applies to SmartOS
 # https://github.com/nodejs/node/issues/43457
 test-report-fatal-error: PASS, FLAKY
+
+[$system==ibmi]
+# https://github.com/nodejs/node/issues/58582
+test-report-exclude-network: PASS,FLAKY