From a62b67c45d7baa7c4c28305617e87c94fdf8774b Mon Sep 17 00:00:00 2001 From: James M Snell Date: Fri, 8 Jan 2021 10:14:59 -0800 Subject: [PATCH] test: mark test-cluster-bind-privileged-port flaky on arm Per rvagg: ``` Persistent failure, even after restarts of the whole cluster. #36478 was merged into this test yesterday but the parent commit still has the failures. What has changed is the Docker version. They all got an upgrade to 5:20.10.2~3-0~raspbian-buster and this is all running inside containers. It's going to be the newest version of Docker running in our CI and I wonder whether we're going to see similar failures when we upgrade other hosts or if this is going to be restricted to ARM. Other than that, I'm not sure what this could be. It seems like a straightforward test that shouldn't fail, maybe Docker has introduced something new for unprivileged port binding inside containers? ``` Signed-off-by: James M Snell --- test/parallel/parallel.status | 3 +++ 1 file changed, 3 insertions(+) diff --git a/test/parallel/parallel.status b/test/parallel/parallel.status index 6639b5ca1a23d8..ff714c7cabfd04 100644 --- a/test/parallel/parallel.status +++ b/test/parallel/parallel.status @@ -36,6 +36,9 @@ test-async-hooks-http-parser-destroy: PASS,FLAKY # https://github.com/nodejs/node/pull/31178 test-crypto-dh-stateless: SKIP test-crypto-keygen: SKIP +# https://github.com/nodejs/node/issues/36847 +test-cluster-bind-privileged-port: PASS,FLAKY +test-cluster-shared-handle-bind-privileged-port: PASS,FLAKY [$system==solaris] # Also applies to SmartOS