Files
node/test/es-module/es-module.status
T
Abdirahim Musse 25f2f27a55 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: https://github.com/nodejs/node/pull/58583
Refs: https://github.com/nodejs/node/issues/58582
Reviewed-By: Joyee Cheung <joyeec9h3@gmail.com>
Reviewed-By: Richard Lau <rlau@redhat.com>
Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
2025-06-06 05:48:13 +00:00

20 lines
568 B
Plaintext

prefix es-module
# To mark a test as flaky, list the test name in the appropriate section
# below, without ".js", followed by ": PASS,FLAKY". Example:
# sample-test : PASS,FLAKY
[true] # This section applies to all platforms
[$system==linux || $system==freebsd]
# https://github.com/nodejs/node/issues/47836
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