Skip to content

Integration tests should use random ports #73

Open
Open
Integration tests should use random ports#73
Assignees
shorstman
Labels
Testing

Description

@EdHurtig
EdHurtig
opened on Nov 12, 2017

For the time being, the integration tests should use randomized ports for Logging and Commands. This will allow mutilple jobs to coexist without deadlocking each other.

In the future we will contain these jobs on the Jenkins server in individual docker containers, etc

Activity

  1. EdHurtig commented on Nov 12, 2017

    @EdHurtig
    EdHurtig
    on Nov 12, 2017
    MemberAuthor

    Related to #62

  2. EdHurtig
    added
    Testing
    on Nov 12, 2017
  3. shorstman
    self-assigned this
    on Nov 12, 2017

  4. shorstman commented on Nov 12, 2017

    @shorstman
    shorstman
    on Nov 12, 2017
    Member

    Is there a range of valid ports/any ports that shouldn't be tested?

  5. EdHurtig commented on Nov 13, 2017

    @EdHurtig
    EdHurtig
    on Nov 13, 2017
    MemberAuthor

    uh anything in the unprivileged port range (I think anything above 1024 IIRC) is fine. Probably best to restrict the range to something like 20,000 to 30,000 and check the random port before starting the test.

    All this logic of port selection can be done in ControllerTest.py

  6. EdHurtig commented on Nov 13, 2017

    @EdHurtig
    EdHurtig
    on Nov 13, 2017
    MemberAuthor

    Alternatively... could use this plugin
    https://wiki.jenkins.io/display/JENKINS/Port+Allocator+Plugin

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

Testing

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions