GitHub user aledsage opened a pull request:

    https://github.com/apache/incubator-brooklyn/pull/300

    Fix more integration tests

    

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

    $ git pull https://github.com/aledsage/incubator-brooklyn 
fix/IntegrationTests-20141104b

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

    https://github.com/apache/incubator-brooklyn/pull/300.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 #300
    
----
commit 1a9636ac9e2eec4cfa6486320befe82fe2b0d8ca
Author: Aled Sage <[email protected]>
Date:   2014-11-04T22:31:17Z

    Add comment to RebindCatalogEntityTest about failure
    
    - Non-deterministic failure seen once on jenkins

commit 00dd84c5b6dcd031ded199810160e10532470849
Author: Aled Sage <[email protected]>
Date:   2014-11-04T22:31:58Z

    Fix MonitIntegrationTest
    
    - monitmysqlwithrestart.monitrc was previously hard-coding OS X!

commit 467b9f7a685335d6b7134dba1a07b55b6c2ece09
Author: Aled Sage <[email protected]>
Date:   2014-11-04T22:33:40Z

    NodeJs: test tidy

commit 5f4cc2d3b7c66b5dde0939d0e9a9aefb62f366cb
Author: Aled Sage <[email protected]>
Date:   2014-11-04T22:56:15Z

    DynamicSequentialTask: handle queue() when task failed
    
    - Previously, in NodeJs’s test detectFailureIfNodeJsBindToPort, it
      would fail non-deterministically because of wrong exception being
      propagated.
    - If an error occurred in a sub-task, and then the main task’s thread 
      called queue(), that call would fail. That failure would be 
      propagated instead of the more interesting child exception.

commit 3eb86535f4b507c892a8912febf0574ec9851df7
Author: Aled Sage <[email protected]>
Date:   2014-11-04T23:06:58Z

    On rmi registry port not available, log what config said

----


---
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