[
https://issues.apache.org/jira/browse/CAMEL-11130?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15964291#comment-15964291
]
Claus Ibsen commented on CAMEL-11130:
-------------------------------------
Ah it seems to run it, but the script needs to be adjusted since the kill
command is different
{code}
Killing Karaf to ensure no dangling karaf running
kill: invalid argument k
Usage:
kill [options] <pid> [...]
Options:
<pid> [...] send signal to every <pid> listed
-<signal>, -s, --signal <signal>
specify the <signal> to be sent
-l, --list=[<signal>] list all signal names, or convert one to a name
-L, --table list all signal names in a nice table
-h, --help display this help and exit
-V, --version output version information and exit
For more details see kill(1).
{code}
And the first CXF test failed with connection not allowed
> 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
>
> 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)
