Remove `common.PORT` usage from `parallel` tests

  • Version: master
  • Platform: all
  • Subsystem: test

Tests in parallel that use common.PORT risk getting EADDRINUSE if another test in parallel uses port 0 (to get an open port assigned by the operating system) at the same time the test runs. This appears to have happened recently. (See #12363 (comment).)

IMO, all instances of common.PORT in parallel should either be changed to use port 0 (if possible in the context of the test) or else moved to sequential (if using port 0 is not possible).

Here are the current tests that use common.PORT: