You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@edgent.apache.org by "Dale LaBossiere (JIRA)" <ji...@apache.org> on 2018/01/30 20:49:00 UTC

[jira] [Resolved] (EDGENT-445) Console testOverridePortNumber() fails in Jenkins

     [ https://issues.apache.org/jira/browse/EDGENT-445?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Dale LaBossiere resolved EDGENT-445.
------------------------------------
       Resolution: Fixed
    Fix Version/s: Apache Edgent 1.3.0

via https://github.com/apache/incubator-edgent/pull/343

> Console testOverridePortNumber() fails in Jenkins
> -------------------------------------------------
>
>                 Key: EDGENT-445
>                 URL: https://issues.apache.org/jira/browse/EDGENT-445
>             Project: Edgent
>          Issue Type: Test
>          Components: Test
>            Reporter: Dale LaBossiere
>            Assignee: Dale LaBossiere
>            Priority: Major
>             Fix For: Apache Edgent 1.3.0
>
>
> The way the test is currently written doesn't seem to work well in the Jenkins test environment (the actual port != expected port).  Hmm... maybe something to do with the j8+j7 tests and the "singleton" HttpServer instance?  Would hope that something would fail if for example the "available port" was no longer available when the server started.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)