You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@geode.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2017/10/02 21:56:00 UTC
[jira] [Commented] (GEODE-3673) LuceneIndexCommandsDUnitTest should
be refactor to use test rules
[ https://issues.apache.org/jira/browse/GEODE-3673?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16188916#comment-16188916 ]
ASF subversion and git services commented on GEODE-3673:
--------------------------------------------------------
Commit 9fa0e5f3258b0cf9831558cb8e700dc6e3ee677c in geode's branch refs/heads/develop from [~upthewaterspout]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=9fa0e5f ]
GEODE-3673: Refactored Lucene commands test to use new framework
The CliCommandTest was causing this test to be flaky. Refactoring to use
the new test framework.
> LuceneIndexCommandsDUnitTest should be refactor to use test rules
> -----------------------------------------------------------------
>
> Key: GEODE-3673
> URL: https://issues.apache.org/jira/browse/GEODE-3673
> Project: Geode
> Issue Type: Bug
> Components: lucene
> Reporter: xiaojian zhou
> Fix For: 1.3.0
>
>
> LuceneIndexCommandsDUnitTest is using CliCommandTestBase, which is a deprecated class. It should be refactored to use more current test rules.
> Currently it becomes flaky:
> org.apache.geode.cache.lucene.internal.cli.LuceneIndexCommandsDUnitTest > describeIndexShouldNotReturnResultWhenIndexNotFound FAILED
> java.lang.AssertionError: Execution of connect --jmx-manager=11911e883462[26198] failed to connect to manager 11911e883462[26198] result=Could not connect to : [host=11911e883462, port=26198]. Failed to retrieve RMIServer stub: javax.naming.CommunicationException [Root exception is java.rmi.NoSuchObjectException: no such object in table]
> at org.apache.geode.management.internal.cli.commands.CliCommandTestBase.connect(CliCommandTestBase.java:272)
> at org.apache.geode.management.internal.cli.commands.CliCommandTestBase.connect(CliCommandTestBase.java:244)
> at org.apache.geode.management.internal.cli.commands.CliCommandTestBase.setUpJmxManagerOnVm0ThenConnect(CliCommandTestBase.java:145)
> at org.apache.geode.cache.lucene.internal.cli.LuceneIndexCommandsDUnitTest.createJMXManager(LuceneIndexCommandsDUnitTest.java:73)
> org.apache.geode.cache.lucene.internal.cli.LuceneIndexCommandsDUnitTest > createIndexShouldCreateANewIndex FAILED
> java.lang.AssertionError: Execution of connect --jmx-manager=11911e883462[27756] failed to connect to manager 11911e883462[27756] result=Could not connect to : [host=11911e883462, port=27756]. Failed to retrieve RMIServer stub: javax.naming.CommunicationException [Root exception is java.rmi.NoSuchObjectException: no such object in table]
> at org.apache.geode.management.internal.cli.commands.CliCommandTestBase.connect(CliCommandTestBase.java:272)
> at org.apache.geode.management.internal.cli.commands.CliCommandTestBase.connect(CliCommandTestBase.java:244)
> at org.apache.geode.management.internal.cli.commands.CliCommandTestBase.setUpJmxManagerOnVm0ThenConnect(CliCommandTestBase.java:145)
> at org.apache.geode.cache.lucene.internal.cli.LuceneIndexCommandsDUnitTest.createJMXManager(LuceneIndexCommandsDUnitTest.java:73)
> To fix it, we should follow the current IndexCommandsDunitTest to refactor. see GEODE-1359.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)