Project

General

Profile

Actions

Bug #17199

closed

[tests] Avoid random port conflicts when bringing up integration test services

Added by Tom Clegg over 3 years ago. Updated over 2 years ago.

Status:
Resolved
Priority:
Normal
Assigned To:
Category:
Tests
Target version:
Story points:
-
Release relationship:
Auto

Description

Occasionally this code in source:sdk/python/tests/run_test_server.py chooses the same port twice, which causes the test suite to fail:

def setup_config():
    rails_api_port = find_available_port()
    controller_port = find_available_port()
    controller_external_port = find_available_port()
    websocket_port = find_available_port()
    websocket_external_port = find_available_port()
    workbench1_port = find_available_port()
    workbench1_external_port = find_available_port()
    # ...

Subtasks 1 (0 open1 closed)

Task #17201: Review 17199-available-port-raceResolvedWard Vandewege12/08/2020Actions
Actions #2

Updated by Ward Vandewege over 3 years ago

Tom Clegg wrote:

17199-available-port-race @ 3083521d8b6c83b0d80e4f63c56ee434ad8fa697 -- developer-run-tests: #2210

LGTM. Of course it won't protect against port numbers being reused accidentally when running multiple copies of run_test_server.py on the same machine...

Actions #3

Updated by Tom Clegg over 3 years ago

port numbers being reused accidentally when running multiple copies of run_test_server.py on the same machine...

Indeed, reliably avoiding that would be a different story...

Actions #4

Updated by Anonymous over 3 years ago

  • Status changed from In Progress to Resolved
Actions #5

Updated by Peter Amstutz over 2 years ago

  • Release set to 41
Actions

Also available in: Atom PDF