summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorRich Trott <rtrott@gmail.com>2021-01-23 04:01:55 -0800
committerMichaƫl Zasso <targos@protonmail.com>2021-02-02 10:47:39 +0100
commit10da5c11047536589b9b21a125ca289e00a6efcd (patch)
tree52f269ff5615580108cd14d5791ab1aaf617c09c
parent5227c5e6f53348967e8f87ae11579b460a104428 (diff)
downloadnode-new-10da5c11047536589b9b21a125ca289e00a6efcd.tar.gz
test: skip tests consistently in parallel.status
Some tests are marked SKIP,FLAKY (resulting in yellow/unstable CI when they fail) and others are marked SKIP (which means the results don't affect CI at all). There doesn't seem to be any reason for the difference. Mark them all as SKIP as IBM i for consistency and to have the luxury of a green daily CI. We'll want these to be at least SKIP,FLAKY (and preferably not skipped at all) before IBM i is supported. PR-URL: https://github.com/nodejs/node/pull/37035 Reviewed-By: Antoine du Hamel <duhamelantoine1995@gmail.com> Reviewed-By: Benjamin Gruenbaum <benjamingr@gmail.com>
-rw-r--r--test/parallel/parallel.status4
1 files changed, 2 insertions, 2 deletions
diff --git a/test/parallel/parallel.status b/test/parallel/parallel.status
index f5bb33cfa6..75d543420d 100644
--- a/test/parallel/parallel.status
+++ b/test/parallel/parallel.status
@@ -70,6 +70,6 @@ test-tls-env-extra-ca: SKIP
# https://github.com/nodejs/node/pull/34209
test-dgram-error-message-address: SKIP
# https://github.com/nodejs/node/issues/36929
-test-crypto-secure-heap: PASS,FLAKY
+test-crypto-secure-heap: SKIP
# https://github.com/nodejs/node/issues/36925
-test-fs-read-type: PASS,FLAKY
+test-fs-read-type: SKIP