You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2018/05/18 13:25:00 UTC
[jira] [Commented] (IGNITE-8381) testNodeSingletonDeploy in Basic 2
has high fail rate
[ https://issues.apache.org/jira/browse/IGNITE-8381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16480639#comment-16480639 ]
ASF GitHub Bot commented on IGNITE-8381:
----------------------------------------
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/3996
> testNodeSingletonDeploy in Basic 2 has high fail rate
> -----------------------------------------------------
>
> Key: IGNITE-8381
> URL: https://issues.apache.org/jira/browse/IGNITE-8381
> Project: Ignite
> Issue Type: Test
> Reporter: Dmitriy Pavlov
> Assignee: Vyacheslav Daradur
> Priority: Major
> Labels: MakeTeamcityGreenAgain, Muted_test
> Fix For: 2.6
>
>
> IgniteServiceConfigVariationsFullApiTestSuite: IgniteServiceConfigVariationsFullApiTest.testNodeSingletonDeploy
> is one from most failing test in TC Run All now
> On dev.list IEP-17 is discussed to redesign services and fix deployemnt. In the same time test itself can't await service to be deployed and confuses Igniters in RunAll PR results.
> It is suggested to find out fast fix to make test passing. It should be probably based on waiting instead of checking deployed state.
> Test history
> https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8&testNameId=1909279554207447487&branch=%3Cdefault%3E&tab=testDetails
> {noformat}
> class org.apache.ignite.IgniteException: Service not found: testService
> at org.apache.ignite.internal.processors.closure.GridClosureProcessor$C2.execute(GridClosureProcessor.java:1858)
> at org.apache.ignite.internal.processors.job.GridJobWorker$2.call(GridJobWorker.java:568)
> at org.apache.ignite.internal.util.IgniteUtils.wrapThreadLoader(IgniteUtils.java:6695)
> at org.apache.ignite.internal.processors.job.GridJobWorker.execute0(GridJobWorker.java:562)
> at org.apache.ignite.internal.processors.job.GridJobWorker.body(GridJobWorker.java:491)
> at org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
> at org.apache.ignite.internal.processors.job.GridJobProcessor.processJobExecuteRequest(GridJobProcessor.java:1189)
> at org.apache.ignite.internal.processors.job.GridJobProcessor$JobExecutionListener.onMessage(GridJobProcessor.java:1921)
> at org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1556)
> at org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:1184)
> at org.apache.ignite.internal.managers.communication.GridIoManager.access$4200(GridIoManager.java:125)
> at org.apache.ignite.internal.managers.communication.GridIoManager$9.run(GridIoManager.java:1091)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748)
> Caused by: class org.apache.ignite.internal.processors.service.GridServiceNotFoundException: Service not found: testService
> at org.apache.ignite.internal.processors.service.GridServiceProxy$ServiceProxyCallable.call(GridServiceProxy.java:415)
> at org.apache.ignite.internal.processors.closure.GridClosureProcessor$C2.execute(GridClosureProcessor.java:1855)
> ... 14 more
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)