mirror of
https://github.com/nodejs/node.git
synced 2025-08-15 13:48:44 +02:00
24065f066f
I missed marking a couple of test cases flaky in my previous PR: https://github.com/nodejs/node/pull/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: https://github.com/nodejs/node/pull/59014#issuecomment-3057162303 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 PR-URL: https://github.com/nodejs/node/pull/59014 Reviewed-By: Richard Lau <richard.lau@ibm.com> Reviewed-By: Luigi Pinca <luigipinca@gmail.com> Reviewed-By: Michael Dawson <midawson@redhat.com>
27 lines
529 B
Text
27 lines
529 B
Text
prefix benchmark
|
|
|
|
# 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
|
|
|
|
# https://github.com/nodejs/node/issues/52690
|
|
test-benchmark-crypto: PASS, FLAKY
|
|
|
|
[$system==win32]
|
|
|
|
[$system==linux]
|
|
|
|
[$system==macos]
|
|
|
|
[$system==solaris] # Also applies to SmartOS
|
|
|
|
[$system==freebsd]
|
|
|
|
[$system==aix]
|
|
|
|
[$arch==arm]
|
|
|
|
[$system==ibmi]
|
|
test-benchmark-websocket: SKIP
|