You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@geode.apache.org by "Jens Deppe (JIRA)" <ji...@apache.org> on 2018/03/18 21:44:00 UTC
[jira] [Updated] (GEODE-4885)
DistributedRestoreSystemPropertiesTest is failing
[ https://issues.apache.org/jira/browse/GEODE-4885?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jens Deppe updated GEODE-4885:
------------------------------
Description:
This test is supposedly checking for any {{DUnitTest}} s that inadvertently run under the {{test}} gradle task or, more specifically, are categorized as {{UnitTest}}.
Unfortunately, due to the way that Junit determines what category a test is in (by creating an instance of the class), it will also invoke any static declarations. It also triggers parameterized values. The result is that some {{DistributedTest}}s actually end up launching DUnit VMs even though the actual tests don't run. Depending on test ordering this can lead to {{DistributedRestoreSystemPropertiesTest}} failing intermittently.
By examining the test report, it appears that the following DUnit tests are triggering this problem:
{noformat}
org.apache.geode.management.internal.cli.commands.ShowLogCommandDUnitTest
org.apache.geode.internal.cache.rollingupgrade.RollingUpgradeDUnitTest
org.apache.geode.security.ClientAuthenticationPart2DUnitTest
org.apache.geode.cache.lucene.LuceneCommandsSecurityDUnitTest
org.apache.geode.management.internal.configuration.ClusterConfigurationIndexWithFromClauseDUnitTest
org.apache.geode.internal.cache.tier.sockets.ClientServerMiscBCDUnitTest
org.apache.geode.cache.lucene.LuceneSearchWithRollingUpgradeDUnit
org.apache.geode.cache.wan.WANRollingUpgradeDUnitTest
org.apache.geode.internal.cache.rollingupgrade.RollingUpgrade2DUnitTest
org.apache.geode.security.ClientAuthenticationDUnitTest
org.apache.geode.security.ClientAuthorizationCQDUnitTest
org.apache.geode.internal.cache.TxCommitMessageBackwardCompatibilityDUnitTest
{noformat}
was:
This test is supposedly checking for any {{DUnitTest}}s that inadvertently run under the {{test}} gradle task or, more specifically, are categorized as {{UnitTest}}.
Unfortunately, due to the way that Junit determines what category a test is in (by creating an instance of the class), it will also invoke any static declarations. It also triggers parameterized values. The result is that some {{DistributedTest}}s actually end up launching DUnit VMs even though the actual tests don't run. Depending on test ordering this can lead to {{DistributedRestoreSystemPropertiesTest}} failing intermittently.
By examining the test report, it appears that the following DUnit tests are triggering this problem:
{noformat}
org.apache.geode.management.internal.cli.commands.ShowLogCommandDUnitTest
org.apache.geode.internal.cache.rollingupgrade.RollingUpgradeDUnitTest
org.apache.geode.security.ClientAuthenticationPart2DUnitTest
org.apache.geode.cache.lucene.LuceneCommandsSecurityDUnitTest
org.apache.geode.management.internal.configuration.ClusterConfigurationIndexWithFromClauseDUnitTest
org.apache.geode.internal.cache.tier.sockets.ClientServerMiscBCDUnitTest
org.apache.geode.cache.lucene.LuceneSearchWithRollingUpgradeDUnit
org.apache.geode.cache.wan.WANRollingUpgradeDUnitTest
org.apache.geode.internal.cache.rollingupgrade.RollingUpgrade2DUnitTest
org.apache.geode.security.ClientAuthenticationDUnitTest
org.apache.geode.security.ClientAuthorizationCQDUnitTest
org.apache.geode.internal.cache.TxCommitMessageBackwardCompatibilityDUnitTest
{noformat}
> DistributedRestoreSystemPropertiesTest is failing
> -------------------------------------------------
>
> Key: GEODE-4885
> URL: https://issues.apache.org/jira/browse/GEODE-4885
> Project: Geode
> Issue Type: Bug
> Components: tests
> Reporter: Jens Deppe
> Priority: Major
>
> This test is supposedly checking for any {{DUnitTest}} s that inadvertently run under the {{test}} gradle task or, more specifically, are categorized as {{UnitTest}}.
> Unfortunately, due to the way that Junit determines what category a test is in (by creating an instance of the class), it will also invoke any static declarations. It also triggers parameterized values. The result is that some {{DistributedTest}}s actually end up launching DUnit VMs even though the actual tests don't run. Depending on test ordering this can lead to {{DistributedRestoreSystemPropertiesTest}} failing intermittently.
> By examining the test report, it appears that the following DUnit tests are triggering this problem:
> {noformat}
> org.apache.geode.management.internal.cli.commands.ShowLogCommandDUnitTest
> org.apache.geode.internal.cache.rollingupgrade.RollingUpgradeDUnitTest
> org.apache.geode.security.ClientAuthenticationPart2DUnitTest
> org.apache.geode.cache.lucene.LuceneCommandsSecurityDUnitTest
> org.apache.geode.management.internal.configuration.ClusterConfigurationIndexWithFromClauseDUnitTest
> org.apache.geode.internal.cache.tier.sockets.ClientServerMiscBCDUnitTest
> org.apache.geode.cache.lucene.LuceneSearchWithRollingUpgradeDUnit
> org.apache.geode.cache.wan.WANRollingUpgradeDUnitTest
> org.apache.geode.internal.cache.rollingupgrade.RollingUpgrade2DUnitTest
> org.apache.geode.security.ClientAuthenticationDUnitTest
> org.apache.geode.security.ClientAuthorizationCQDUnitTest
> org.apache.geode.internal.cache.TxCommitMessageBackwardCompatibilityDUnitTest
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)