adapt test-ci build target for buildd

Forwarded: not-needed
Reviewed-By: Xavier Guimard <yadd@debian.org>
Last-Update: 2020-02-09

* run tests with ./node
* remove addons from test-ci suite, because it creates a dependency loop
  nodejs -> node-gyp -> nodejs which is painful to manage.
* disabled because it requires stdin:
  + test-stdout-close-unref
  + test-regress-GH-746
* test-tick-processor fails on ppc64 and s390x, currently investigated
  https://github.com/nodejs/node/issues/2471
* test-cluster-disconnect sometimes fails on busy buildd, forwarded upstream
  https://github.com/nodejs/node/issues/3383
* test-fs-watch is flaky, might be related to https://github.com/nodejs/node/issues/4082
* huge timeout value for all platforms, buildd could be busy
* test-npm-install and test-release-npm must fail, debian package dfsg-repacked npm out
* ability to override CI_NATIVE_SUITES, CI_JS_SUITES
* disable tests failing because DNS is disabled
* sequential/test-http2-session-timeout is flaky https://github.com/nodejs/node/issues/20628

Gbp-Pq: Topic build
Gbp-Pq: Name test_ci.patch

diff --git a/Makefile b/Makefile
index 85962ae94329d6548b65a108d90fa44f1f17d86c..fabbb36260ad8e684a7c06fac78da412c8d992f1 100644 (file)
--- a/Makefile
+++ b/Makefile
@@ -556,7 +556,7 @@ test-ci-native: | benchmark/napi/.buildstamp test/addons/.buildstamp test/js-nat
 # This target should not use a native compiler at all
 # Related CI job: node-test-commit-arm-fanned
 test-ci-js: | clear-stalled
-       $(PYTHON) tools/test.py $(PARALLEL_ARGS) -p tap --logfile test.tap \
+       $(PYTHON) tools/test.py $(PARALLEL_ARGS) -p tap \
                --mode=$(BUILDTYPE_LOWER) --flaky-tests=$(FLAKY_TESTS) \
                --skip-tests=$(CI_SKIP_TESTS) \
                $(TEST_CI_ARGS) $(CI_JS_SUITES)

diff --git a/test/common/index.js b/test/common/index.js
index 75f51fb06cc24233e8a724d576aec001d452cf6f..096106fa1901027d20358f1a6f5b8ab96bb6e299 100644 (file)
--- a/test/common/index.js
+++ b/test/common/index.js
@@ -278,16 +278,15 @@ const pwdCommand = isWindows ?
 
 function platformTimeout(ms) {
   const multipliers = typeof ms === 'bigint' ?
-    { two: 2n, four: 4n, seven: 7n } : { two: 2, four: 4, seven: 7 };
+    { fast: 2n, slow: 4n } : { fast: 3, slow: 5 };
+ 
+  if (process.arch.startsWith('arm') || process.arch.startsWith('mips') || process.arch.startsWith('riscv'))
+    ms = multipliers.slow * ms;
+  else
+    ms = multipliers.fast * ms;
 
   if (process.features.debug)
-    ms = multipliers.two * ms;
-
-  if (exports.isAIX || exports.isIBMi)
-    return multipliers.two * ms; // Default localhost speed is slower on AIX
-
-  if (isPi)
-    return multipliers.two * ms;  // Raspberry Pi devices
+    ms = multipliers.slow * ms;
 
   return ms;
 }

diff --git a/test/parallel/parallel.status b/test/parallel/parallel.status
index 28f25e4be7e3104894e53a22e50f5474e0b7bc76..b538eea7d347ca0ef70647ea5b20dd068c638ea1 100644 (file)
--- a/test/parallel/parallel.status
+++ b/test/parallel/parallel.status
@@ -22,6 +22,48 @@ test-error-serdes: PASS, FLAKY
 # https://github.com/nodejs/node/issues/54006
 test-sqlite: PASS, FLAKY
 
+test-process-config                  : PASS,FLAKY
+test-regress-GH-746                  : PASS,FLAKY
+test-stdout-close-unref              : PASS,FLAKY
+test-npm-install                     : FAIL
+test-npm-version                     : FAIL
+test-release-npm                     : FAIL
+# skip tests accessing network
+test-dns                             : SKIP
+test-net-connect-immediate-finish    : SKIP
+test-net-better-error-messages-port-hostname : SKIP
+
+# in debian build env, skip because it somehow tries to access network
+test-https-connect-address-family : SKIP 
+test-tls-connect-address-family : SKIP
+test-dns-cancel-reverse-lookup: SKIP
+test-dns-resolveany-bad-ancount: SKIP
+
+# https://bugs.debian.org/919588
+## flaky on some user environments
+test-net-listen-after-destroying-stdin: PASS,FLAKY
+## fails when running with eatmydata
+test-fs-error-messages: PASS,FLAKY
+
+# this new test doesn't have a built target properly setup
+test-child-process-stdio-overlapped: SKIP
+
+# does not pass in autopkgtest ci env
+test-cluster-bind-privileged-port: PASS,FLAKY
+test-cluster-shared-handle-bind-privileged-port: PASS,FLAKY
+test-debugger-preserve-breaks: PASS,FLAKY
+
+# for debian buildd i386 (but pass on porter barriere.d.o)
+test-debugger-heap-profiler: PASS,FLAKY
+
+# corepack is dfsg-excluded
+test-corepack-yarn-install: SKIP
+test-corepack-version: SKIP
+
+# fails on 32-bits arch, see #1069753
+test-fs-utimes: PASS,FLAKY
+test-fs-utimes-y2K38: PASS,FLAKY
+
 [$system==win32]
 
 # Windows on x86
@@ -53,6 +95,10 @@ test-crypto-keygen: SKIP
 # https://github.com/nodejs/node/issues/52963
 test-pipe-file-to-http: PASS, FLAKY
 
+[$arch==mips64el]
+# the debug flag is for hacking v8 internals
+test-debug-args: PASS,FLAKY
+
 [$system==solaris] # Also applies to SmartOS
 # https://github.com/nodejs/node/issues/43457
 test-domain-no-error-handler-abort-on-uncaught-0: PASS, FLAKY
@@ -104,9 +150,10 @@ test-tls-write-error: PASS, FLAKY
 # https://github.com/nodejs/node/issues/48047
 test-http-pipeline-flood: SKIP
 
-[$asan==on]
+# flaky on sbuild
 # https://github.com/nodejs/node/issues/39655
 test-cluster-primary-error: PASS, FLAKY
+test-cluster-primary-kill: PASS, FLAKY
 
 [$arch==loong64]
 # https://github.com/nodejs/node/issues/51662

diff --git a/test/sequential/sequential.status b/test/sequential/sequential.status
index ccab879b6e5fcdcc0d3a4b790b97db94d92f1a59..7998811aea4a86a90541ff33599c633d212eefed 100644 (file)
--- a/test/sequential/sequential.status
+++ b/test/sequential/sequential.status
@@ -7,12 +7,29 @@ prefix sequential
 [true] # This section applies to all platforms
 # https://github.com/nodejs/node/issues/27611#issuecomment-613100468
 test-cpu-prof-dir-worker: PASS, FLAKY
+test-cpu-prof-dir-absolute: PASS,FLAKY
 # https://github.com/nodejs/node/issues/44898
 test-watch-mode: PASS, FLAKY
 test-watch-mode-inspect: PASS, FLAKY
 # https://github.com/nodejs/node/issues/47409
 test-http2-large-file: PASS, FLAKY
 
+# flaky or failing at least on debian build servers
+test-fs-watch                                   : PASS,FLAKY
+test-force-repl                                 : SKIP
+test-performance                                : SKIP
+test-http2-session-timeout                      : PASS,FLAKY
+test-debugger-preserve-breaks                   : PASS,FLAKY
+test-debugger-exec-scope                        : PASS,FLAKY
+test-worker-heapsnapshot-options                : PASS,FLAKY
+
+# https://github.com/nodejs/node/issues/24403
+test-cli-syntax: PASS,FLAKY
+
+# new test - failing/hanging https://github.com/nodejs/node/issues/44898
+test-watch-mode: SKIP
+test-watch-mode-inspect: SKIP
+
 [$system==win32]
 # https://github.com/nodejs/node/issues/47116
 test-http-max-sockets: PASS, FLAKY