GitHub user drigodwin opened a pull request:

    https://github.com/apache/brooklyn-library/pull/106

    [WIP] Fix GeoDNS tests

    The GEODNS tests are currently failing:
    ```
     2017-05-10 03:59:21,695 ERROR Problem refreshing group membership: 
org.apache.brooklyn.util.exceptions.RuntimeInterruptedException: 
java.lang.InterruptedException
    org.apache.brooklyn.util.exceptions.RuntimeInterruptedException: 
java.lang.InterruptedException
        at 
org.apache.brooklyn.util.exceptions.Exceptions.propagate(Exceptions.java:124) 
~[brooklyn-utils-common-0.12.0-SNAPSHOT.jar:0.12.0-SNAPSHOT]
    Caused by: java.lang.InterruptedException: null
        at java.util.concurrent.FutureTask.awaitDone(FutureTask.java:404) 
[na:1.8.0_121]
    Tests run: 42, Failures: 1, Errors: 0, Skipped: 22, Time elapsed: 57.834 
sec <<< FAILURE! - in TestSuite
    tearDown(org.apache.brooklyn.entity.dns.AbstractGeoDnsServiceTest)  Time 
elapsed: 31.464 sec  <<< FAILURE!
    org.testng.internal.thread.ThreadTimeoutException: Method 
org.apache.brooklyn.core.test.BrooklynMgmtUnitTestSupport.tearDown() didn't 
finish within the time-out 30000
    
    
    Results :
    
    Failed tests: 
      
AbstractGeoDnsServiceTest>BrooklynMgmtUnitTestSupport.tearDown:58->BrooklynMgmtUnitTestSupport.destroyManagementContextSafely:71
 » ThreadTimeout
    ```
    This swaps them to integration tests.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/drigodwin/brooklyn-library fix-geo-tests

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/brooklyn-library/pull/106.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #106
    
----

----


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---

Reply via email to