You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Tadayoshi Sato (JIRA)" <ji...@apache.org> on 2017/04/13 02:26:41 UTC

[jira] [Assigned] (CAMEL-11130) Jenkins - Camel.trunk.itest.karaf doesn't run all tests in camel-itest-karaf

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

Tadayoshi Sato reassigned CAMEL-11130:
--------------------------------------

    Assignee: Tadayoshi Sato

> Jenkins - Camel.trunk.itest.karaf doesn't run all tests in camel-itest-karaf
> ----------------------------------------------------------------------------
>
>                 Key: CAMEL-11130
>                 URL: https://issues.apache.org/jira/browse/CAMEL-11130
>             Project: Camel
>          Issue Type: Test
>          Components: karaf, tests
>    Affects Versions: 2.19.0
>            Reporter: Tadayoshi Sato
>            Assignee: Tadayoshi Sato
>             Fix For: 2.19.0
>
>
> Jenkins job Camel.trunk.itest.karaf https://builds.apache.org/view/A-D/view/Camel/job/Camel.trunk.itest.karaf/ at first seems to pass green, but in reality it silently fails earlier and doesn't complete all the tests. It's because of phantom Karaf instances spawned in each test but somehow not being terminated normally.
> The consequence of this job not working is constant creeping in of dependency upgrades that break component features, thus jeopardising the reliability of using components on Karaf through features.
> Locally, instead of {{mvn test}} running {{./run-tests.sh}} can complete the test suite, so it is great if in some way we can use the script in the Jenkins job.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)