During tests, the Jetty server was started manually running the jar file, and 
the PID file was not generated. This caused the stop statement to silently fail 
and Jetty kept running. This change also removes a graceful wait used in live 
tests that does not make sense in stubbed integration tests.
You can view, comment on, or merge this pull request online at:

  https://github.com/jclouds/jclouds/pull/1087

-- Commit Summary --

  * Fix the Jetty start statement used in compute live tests

-- File Changes --

    M compute/src/test/java/org/jclouds/compute/JettyStatements.java (7)
    M 
compute/src/test/java/org/jclouds/compute/StubComputeServiceIntegrationTest.java
 (10)
    M 
compute/src/test/java/org/jclouds/compute/internal/BaseComputeServiceLiveTest.java
 (6)

-- Patch Links --

https://github.com/jclouds/jclouds/pull/1087.patch
https://github.com/jclouds/jclouds/pull/1087.diff

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/1087

Reply via email to