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 <jasnell@gmail.com> PR-URL: https://github.com/nodejs/node/pull/36850 Refs: https://github.com/nodejs/node/issues/36847 Reviewed-By:
Michael Dawson <midawson@redhat.com> Reviewed-By:
Mary Marchini <oss@mmarchini.me>
parent
db12ece8
Please register or sign in to comment