Details
-
Test
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
None
-
None
Description
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.