Page MenuHomePhabricator

Reduce port range in functional tests
ClosedPublic

Authored by Fabien on Wed, Apr 24, 13:57.

Details

Reviewers
PiRK
Group Reviewers
Restricted Project
Commits
rABC3b3c5674a35b: Reduce port range in functional tests
Summary

So that we never use port number > 32000.
Docker uses ports 32768-65535 for its own use (containerd) so there is a risk of collision that can be avoided by reducing the range.

Test Plan

In various conditions, with chronik enabled (the only tests that can reach ports > 28000):

ninja check-functional

See CI calls in the comments in this diff.

Diff Detail

Repository
rABC Bitcoin ABC
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

@bot build-linux32 build-linux64 build-linux-arm build-linux-aarch64 build-chronik build-chronik-plugins

@bot build-linux32 build-linux64 build-linux-arm build-linux-aarch64 build-chronik build-chronik-plugins

@bot build-linux32 build-linux64 build-linux-arm build-linux-aarch64 build-chronik build-chronik-plugins

@bot build-linux32 build-linux64 build-linux-arm build-linux-aarch64 build-chronik build-chronik-plugins

@bot build-linux32 build-linux64 build-linux-arm build-linux-aarch64 build-chronik build-chronik-plugins

Fabien published this revision for review.Wed, Apr 24, 15:50
Fabien edited the summary of this revision. (Show Details)
Fabien edited the test plan for this revision. (Show Details)
This revision is now accepted and ready to land.Wed, Apr 24, 20:36
This revision was automatically updated to reflect the committed changes.