Commit 9d25d25
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: #36850
Refs: #36847
Reviewed-By: Michael Dawson <midawson@redhat.com>
Reviewed-By: Mary Marchini <oss@mmarchini.me>1 parent c64db20 commit 9d25d25
1 file changed
Lines changed: 3 additions & 0 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
@@ -36,6 +36,9 @@ test-async-hooks-http-parser-destroy: PASS,FLAKY | |||
| 36 | 36 | # https://github.com/nodejs/node/pull/31178 | |
| 37 | 37 | test-crypto-dh-stateless: SKIP | |
| 38 | 38 | test-crypto-keygen: SKIP | |
| 39 | + # https://github.com/nodejs/node/issues/36847 | ||
| 40 | + test-cluster-bind-privileged-port: PASS,FLAKY | ||
| 41 | + test-cluster-shared-handle-bind-privileged-port: PASS,FLAKY | ||
| 39 | 42 | ||
| 40 | 43 | [$system==solaris] # Also applies to SmartOS | |
| 41 | 44 | ||
0 commit comments