[
https://issues.apache.org/jira/browse/IGNITE-18251?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ilya Shishkov updated IGNITE-18251:
-----------------------------------
Description:
Currently, TeamCity runs tests twice, because test classes are not specified.
It leads to running of both suite classes and test classes, included to this
test suites. Arguments are listed below [1]:
{code}
-pl modules/%DIR_EXTENSION% -am
-Dmaven.test.failure.ignore=true
-DfailIfNoTests=false
-Dignite.version=%IGNITE_VERSION%
{code}
Also, there are following problems:
# Timeouts of CDC Suite
# Zookeeper Ip Finder and AOP has no running test on TC [2, 3].
What should be done:
# Split {{IgniteCdcTestSuite}} class on two separate classes.
# Make two separate TC builds for corresponding CDC suite classes.
# Fix Zookeeper Ip Finder and AOP modules testing.
Links:
#
https://ci2.ignite.apache.org/admin/editRunType.html?id=template:IgniteExtensions_Tests_RunExtensionTests&runnerId=RUNNER_141&cameFromUrl=%2Fadmin%2FeditBuildRunners.html%3Fid%3Dtemplate%253AIgniteExtensions_Tests_RunExtensionTests%26init%3D1&cameFromTitle=
#
https://ci2.ignite.apache.org/buildConfiguration/IgniteExtensions_Tests_ZookeeperIpFinder?branch=&mode=builds#all-projects
#
https://ci2.ignite.apache.org/buildConfiguration/IgniteExtensions_Tests_Aop?mode=builds#all-projects
P.S.
*_So, there are possible solutions:_*
# Remove {{IgniteCdcTestSuite}} class without changing TC confiuration.
# Split {{IgniteCdcTestSuite}} onto to suite classes, eg. Ignite2Ignite and
IgniteThroughKafka. This also makes possible to run suites separately, but
requires changing TC configuration.
Also, we can add explicit suite classes in TC configuration, but it is makes
sense only if we have to to run suites in parallel manner for some modules. If
I'm right, only CDC is now a possible candidate for this.
was:
As I see, now CDC Test Suite on both TC instances runs tests twice:
*Duplication in TC1 build #350:*
{quote}[22:39:32] : [Step 3/3] [22:39:32] >>> Starting test class:
CdcIgniteToIgniteReplicationTest <<<
[23:00:48] : [Step 3/3] [23:00:48] >>> Starting test class:
ConflictResolverRestartTest <<<
[23:00:50] : [Step 3/3] [23:00:50] >>> Starting test class:
CacheConflictOperationsTest <<<
[23:00:51] : [Step 3/3] [23:00:51] >>> Starting test class:
CdcKafkaReplicationAppsTest <<<
[00:13:57] : [Step 3/3] [00:13:57] >>> Starting test class:
KafkaToIgniteLoaderTest <<<
[00:13:57] : [Step 3/3] [00:13:57] >>> Starting test class:
CdcKafkaReplicationTest <<<
{color:#de350b}[01:22:21] : [Step 3/3] [01:22:21] >>> Starting test class:
CacheConflictOperationsWithFieldTest <<<{color}
{color:#de350b}[01:22:21] : [Step 3/3] [01:22:21] >>> Starting test class:
CacheConflictOperationsTest <<<{color}
{color:#de350b}[01:22:22] : [Step 3/3] [01:22:22] >>> Starting test class:
CacheConflictOperationsWithFieldTest <<<{color}
{color:#de350b}[01:22:23] : [Step 3/3] [01:22:23] >>> Starting test class:
CdcIgniteToIgniteReplicationTest <<<{color}
{quote}
*Duplication in TC2 build #285:*
{quote}[23:14:52] : [Step 3/3] [23:14:52] >>> Starting test class:
ConflictResolverRestartTest <<<
[23:14:55] : [Step 3/3] [23:14:55] >>> Starting test class:
CdcIgniteToIgniteReplicationTest <<<
[23:33:07] : [Step 3/3] [23:33:07] >>> Starting test class:
CacheConflictOperationsTest <<<
[23:33:08] : [Step 3/3] [23:33:08] >>> Starting test class:
CacheConflictOperationsWithFieldTest <<<
[23:33:09] : [Step 3/3] [23:33:09] >>> Starting test class:
CdcIgniteToIgniteReplicationTest <<<
[23:51:14] : [Step 3/3] [23:51:14] >>> Starting test class:
KafkaToIgniteLoaderTest <<<
[23:51:15] : [Step 3/3] [23:51:15] >>> Starting test class:
CdcKafkaReplicationTest <<<
[00:32:29] : [Step 3/3] [00:32:29] >>> Starting test class:
CdcKafkaReplicationAppsTest <<<
{color:#de350b}[01:14:03] : [Step 3/3] [01:14:03] >>> Starting test class:
ConflictResolverRestartTest <<<{color}
{color:#de350b}[01:14:04] : [Step 3/3] [01:14:04] >>> Starting test class:
CacheConflictOperationsWithFieldTest <<<{color}
{color:#de350b}[01:14:04] : [Step 3/3] [01:14:04] >>> Starting test class:
KafkaToIgniteLoaderTest <<<{color}
{color:#de350b}[01:14:04] : [Step 3/3] [01:14:04] >>> Starting test class:
CdcKafkaReplicationAppsTest <<<{color}
{color:#de350b}[01:14:04] >>> Starting test class: KafkaToIgniteLoaderTest
<<<{color}
{color:#de350b}[01:55:29] : [Step 3/3] [01:55:29] >>> Starting test class:
CdcKafkaReplicationTest <<<{color}
{quote}
It seems, that tests implicitly runs outside of the scope
{{{}IgniteCdcTestSuite{}}}. We should remove such duplication, _because of
execution timeout_ which blocks testing of CDC extension. Moreover, we should
check, that other extensions are tested without such duplication.
Build logs:
# TC1: [^_TESTS_CDC_350.log.zip]
# TC2: [^_TESTS_CDC_285.log.zip]
Links on corresponding TC build:
# [TC1 build
#350|https://ci.ignite.apache.org/buildConfiguration/IgniteExtensions_Tests_Cdc/6922925?buildTab=overview&hideProblemsFromDependencies=false&expandBuildTestsSection=true&hideTestsFromDependencies=false&expandBuildChangesSection=true&expandBuildProblemsSection=true]
# [TC2 build
#285|https://ci2.ignite.apache.org/buildConfiguration/IgniteExtensions_Tests_Cdc/6919480?expandBuildProblemsSection=true&hideProblemsFromDependencies=false&expandBuildTestsSection=true&hideTestsFromDependencies=false&expandBuildChangesSection=true]
P.S.
*_So, there are possible solutions:_*
# Remove {{IgniteCdcTestSuite}} class without changing TC confiuration.
# Split {{IgniteCdcTestSuite}} onto to suite classes, eg. Ignite2Ignite and
IgniteThroughKafka. This also makes possible to run suites separately, but
requires changing TC configuration.
Also, we can add explicit suite classes in TC configuration, but it is makes
sense only if we have to to run suites in parallel manner for some modules. If
I'm right, only CDC is now a possible candidate for this.
> Refactor testing of ignite-extensions
> -------------------------------------
>
> Key: IGNITE-18251
> URL: https://issues.apache.org/jira/browse/IGNITE-18251
> Project: Ignite
> Issue Type: Task
> Components: extensions
> Reporter: Ilya Shishkov
> Priority: Major
> Labels: ise, teamcity
>
> Currently, TeamCity runs tests twice, because test classes are not specified.
> It leads to running of both suite classes and test classes, included to this
> test suites. Arguments are listed below [1]:
> {code}
> -pl modules/%DIR_EXTENSION% -am
> -Dmaven.test.failure.ignore=true
> -DfailIfNoTests=false
> -Dignite.version=%IGNITE_VERSION%
> {code}
> Also, there are following problems:
> # Timeouts of CDC Suite
> # Zookeeper Ip Finder and AOP has no running test on TC [2, 3].
> What should be done:
> # Split {{IgniteCdcTestSuite}} class on two separate classes.
> # Make two separate TC builds for corresponding CDC suite classes.
> # Fix Zookeeper Ip Finder and AOP modules testing.
> Links:
> #
> https://ci2.ignite.apache.org/admin/editRunType.html?id=template:IgniteExtensions_Tests_RunExtensionTests&runnerId=RUNNER_141&cameFromUrl=%2Fadmin%2FeditBuildRunners.html%3Fid%3Dtemplate%253AIgniteExtensions_Tests_RunExtensionTests%26init%3D1&cameFromTitle=
> #
> https://ci2.ignite.apache.org/buildConfiguration/IgniteExtensions_Tests_ZookeeperIpFinder?branch=&mode=builds#all-projects
> #
> https://ci2.ignite.apache.org/buildConfiguration/IgniteExtensions_Tests_Aop?mode=builds#all-projects
> P.S.
> *_So, there are possible solutions:_*
> # Remove {{IgniteCdcTestSuite}} class without changing TC confiuration.
> # Split {{IgniteCdcTestSuite}} onto to suite classes, eg. Ignite2Ignite and
> IgniteThroughKafka. This also makes possible to run suites separately, but
> requires changing TC configuration.
> Also, we can add explicit suite classes in TC configuration, but it is makes
> sense only if we have to to run suites in parallel manner for some modules.
> If I'm right, only CDC is now a possible candidate for this.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
