camel-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CAMEL-11130) Jenkins - Camel.trunk.itest.karaf doesn't run all tests in camel-itest-karaf
Date Thu, 13 Apr 2017 10:40:41 GMT

    [ https://issues.apache.org/jira/browse/CAMEL-11130?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15967389#comment-15967389
] 

ASF GitHub Bot commented on CAMEL-11130:
----------------------------------------

Github user asfgit closed the pull request at:

    https://github.com/apache/camel/pull/1625


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

Mime
View raw message